The unique constraint changes are reverted in 4.1.12-SNAPSHOT.
I'm following this discussion up with
https://hibernate.atlassian.net/browse/HHH-8162. Any further comments, please
leave them there. Thanks!
Brett Meyer
Red Hat Software Engineer, Hibernate
- Original Message -
From: "Br
https://github.com/hibernate/hibernate-orm/commit/409ca769258cd4bfc67761d9cf0fca1ab56e
That reverted HHH-7797 in 4.1. I just kicked off a build & snapshot release.
I'd feel much more comfortable about releasing 4.1.12.Final if some of you
could grab and test 4.1.12-SNAPSHOT, once it's fini
We cannot simply remove unique constraint generation on an update all-together
-- although you have a good point about the exceptions, many users still rely
on that functionality. Instead, let's make it configurable. A property would
select from the following:
1.) Update ignores all unique co
Hi Brett,
Thanks for following up on this. My comments below.
On Fri, Apr 5, 2013 at 6:44 PM, Brett Meyer wrote:
> Here's what I'd like to do. In 4.1.x, all of the unique
> constraint/index/column changes from HHH-7797 [1] and the random constraint
> names in HHH-1904 [2] will be reverted. W
Here's what I'd like to do. In 4.1.x, all of the unique
constraint/index/column changes from HHH-7797 [1] and the random constraint
names in HHH-1904 [2] will be reverted. When we originally started working on
them, they weren't intended to be this complex. We'll cut a new 4.1.x release.
Bu
