Gavin King
Gavin King
> Tomcat's JDBC pool implementation does not correctly wrap the full chain of objects, meaning the raw Statement can be retrieved from a ResultSet rather than returning the proxied statement....
> I'm fine with the change. I agree with @mc1arke that it, at worst, makes Hibernate more robust. OK, fine. I withdraw my objection.
@andreitokar But that makes no sense from the perspective of the user. The user created a constraint named `count_name_key`. If the user wanted a constraint named `COUNT_NAME_KEY_INDEX_2` they would have...
@lorenzbaier > i have the same issue but it seems like it orignates from not even setting the constraint name in the DDL The `name` member of the JPA-standard `@UniqueConstraint`...
@fheck So it's correct in the latest release then.
> @gavinking is there a changelog which reports this new behaviour of hibernate not generating the constraint names anymore? There is no such "new behavior". I mean, in the original...
I really don't know what you're asking about, since it's clear that Hibernate DDL generation is respecting all user-specified constraint names. And I don't know why you think the issue...
I really don't understand the resistance to fixing this issue. If the user creates a unique constraint with an explicit name like `count_name_key`, then h2 should report violations of that...
Excellent, thanks so much for fixing this!