[hibernate-dev] 4.1.x and HHH-8092 aka no unique constraints after 4.1.10 upgrade

[Brett Meyer]

Guillaume, here's what I'd propose.  I'll cherry-pick the fix into the 4.1 branch.  Can you grab that from git (or I'll re-enable the 4.1 builds temporary and push out a new SNAPSHOT) and re-test?  Before I release another 4.1.x, I'd like some feedback on whether or not HHH-8092 was sufficient, or if there are other additional issues that might merit reverting the HHH-7797 change in 4.1 entirely.  In retrospect, it quickly became a big enough fix that it probably should have been kept out of 4.1 to begin with...

Once that's nailed down, I don't have a problem cutting another 4.1.x release.

Thanks for your help!

Brett Meyer
Red Hat Software Engineer, Hibernate

----- Original Message -----
From: "Guillaume Smet" <guillaume.smet at gmail.com>
To: "Hibernate" <hibernate-dev at lists.jboss.org>
Sent: Wednesday, April 3, 2013 10:52:28 AM
Subject: [hibernate-dev] 4.1.x and HHH-8092 aka no unique constraints after	4.1.10 upgrade

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 at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev