Hi, Will you please try the latest check-in 713778? I have essentially reverted to 1.1.0 scheme of naming the constraints. If possible use a database that does *not* allow identically named constraints across different tables (e.g. HSQLDB, I presume). Also see if the associated test cases can be bolstered.
The problem of generating unique naming could have had a simpler solution if JPA spec allowed a constraintName attribute for @UniqueConstraint and @Column(unique=true). Pinaki -- View this message in context: http://n2.nabble.com/Schema-generation-with-unique-constraints-tp1469373p1495039.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
