[
https://issues.apache.org/jira/browse/OPENJPA-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milosz Tylenda resolved OPENJPA-709.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-M4
1.3.0
I believe this has been fixed some time ago in the trunk and 1.3.x branch.
A test case can be seen here:
http://svn.apache.org/viewvc/openjpa/trunk/openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/persistence/jdbc/unique/
> Better naming for unique constraints
> ------------------------------------
>
> Key: OPENJPA-709
> URL: https://issues.apache.org/jira/browse/OPENJPA-709
> Project: OpenJPA
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Environment: SUN JDK 1.6.0_06 for Linux(amd64)
> Reporter: Georgi Naplatanov
> Priority: Trivial
> Fix For: 1.3.0, 2.0.0-M4
>
>
> An unique constraint name contains "uk_" prefix and combination of field's
> names. In case two or more tables have unique constraints with the same
> combination of fields, the generation of database's schema will fail, because
> constraint name should be unique too.
> It will be very nice if next versions of JPA specification will include
> possibility to set name for particular constraint.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
