AFAIK, it is an oracle specific constraint to not allow both a unique and primary key
constraint on the same column. It certainly works fine with postgresql and DB2.
As for where the bug actually lies, that's a good question. Probably need to file a
bug against hbm2ddl to drop the unique constraint on Id columns for Oracle. But there are
other places to fix it, obviously.
I'm surprised you're the first one to find this.
Devon
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075615#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...