Hibernate 4.2.0.Final (EAP 6.1.0) included changes to how unique keys and foreign keys were generated (both default to using constraints in "alter table" statements). Multiple issues were found and fixed in commits spanning 4.2.1.Final to 4.2.3.Final. This is fairly high priority and should be considered for EAP 6.1.1. It may affect anyone using schema generation and un-named unique or foreign keys. https://hibernate.atlassian.net/browse/HHH-1904 https://hibernate.atlassian.net/browse/HHH-8092 https://hibernate.atlassian.net/browse/HHH-8178 https://hibernate.atlassian.net/browse/HHH-8162 https://hibernate.atlassian.net/browse/HHH-8217 https://hibernate.atlassian.net/browse/HHH-8269 https://hibernate.atlassian.net/browse/HHH-8273 https://hibernate.atlassian.net/browse/HHH-8275
Note that there may be some concerns about backward compatability with the fixes. They do change the strategy used for automatic generation of constraint names. However, we're specifically fixing issues where this generation was not deterministic in 4.2.0.Final, so it's a moot point.
Pushed to http://git.app.eng.bos.redhat.com/?p=hibernate/hibernate-core.git;a=shortlog;h=refs/heads/eap61-cp-updates
*** This bug has been marked as a duplicate of bug 981720 ***
Removing flags (not to see this bz in ACK_VIEW)