Sounds like a bug. If you open a JIRA it can be confirmed.

Then you can provide a patch and someone will test and commit it. ;-)

Craig

On Jul 8, 2009, at 11:46 AM, Laird Nelson wrote:

I wanted to confirm this bug here before I recorded it.

If I have two columns in my entity that are both marked @Column( ... unique = true), then the DDL generation machinery of OpenJPA attempts to create two unique constraints, one for each column--so far so good--but with the same constraint name of _UNQ. The H2 database, at least, does not permit two
unique constraints to have the same identifier.

Can someone confirm that this is a bug, and, if so, I will enter it into
JIRA.

Thanks,
Laird

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to