Hi, Sorry for bothering you with this, but we just got hit by https://hibernate.atlassian.net/browse/HHH-8092 in our applications after an upgrade to 4.1.11 (we worked on fixes included in 4.1.10 and needed the upgrade to get our bugs fixed).
Due to HHH-8092, with 4.1.10 and 4.1.11, our unique constraints are not created anymore as we use the hbm2ddl update mode. And we cannot use 4.1.9 due to the issues we helped fixing for 4.1.10. I know that 4.1.11 was supposed to be the very last version of the 4.1.x cycle but it seems to me it's not really possible to have the last 4.1.x version so broken in a way which can have consequences on your data in very common cases. FWIW, we tried to upgrade to 4.2.x but we have other regressions which will need time to get diagnosed and fixed. So we won't be able to use 4.2.1 soon, even after its release. Would you consider backporting the fix for HHH-8092 to the 4.1.x branch and release a new version? I'm pretty sure there are a lot of people using @UniqueConstraint and the hbm2ddl update mode and they will get hit by this problem pretty hard. It looks to me like a major regression, which isn't usually compatible with an end of cycle release supposed to be quite stable. Thanks for your feedback. -- Guillaume _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
