Missing auto generated constraint names on h2 ddl
Description
Activity
Gavin King April 4, 2024 at 4:17 PM
No problem, all my notifications were going absolutely crazy today and I’m snowed under.
For the record, if you’re interested to see how and why this change occurred, you can search through the issues here (there were many recent fixes relating to unique keys in DDL) or through the pull requests on GitHub. All the information is available in public. Obviously we have to be selective about what to include in the migration guide or release announcement. This isn’t the sort of thing we would normally include, because it principle it should not break sensibly-written programs.
Lorenz Baier April 4, 2024 at 3:19 PM
@Gavin King hey Gavin, I didn’t mean to offend you. I just thought ,since the problem was related to your original h2 issue, that you can point me to some documentation of this breaking change. But I don’t want to force or expect you to prioritize my issue.
Have a nice day 😄
Gavin King April 4, 2024 at 2:13 PM
(I did ask you to take this to the forum. Not to JIRA.)
Gavin King April 4, 2024 at 2:13 PM
Lorenz, Hibernate has hundreds of thousands of users and a handful of developers. Do you really think that it is an efficient use of the limited resources available to maintain this project to be harassing me over this thing?
Do you really think it’s better for me to waste an hour of my day on this, instead of spending that time resolving the last few things that are blocking the release of Jakarta Data 1.0?
If you really think this is something that needs to be mentioned in the migration guide, you could of course be a good citizen of this open source community, and go, track down the pull request that caused this change, and send us a pull request updating the migration guide.
Lorenz Baier April 4, 2024 at 2:02 PM
@Gavin King maybe i should not rely on it but is there a changelog explaining that change?
hibernate 6.4.4.Final/h2 2.2.224 generates:
create table "point" ... unique ("number", "parent_version_identifier"), unique ("code", "parent_version_identifier"))hibernate 6.2.13.Final/h2 2.2.214 generates
create table "point" ... constraint "UK1234566" unique ("number", "parent_version_identifier"), constraint "UK123456safseef6" unique ("code", "parent_version_identifier"))i expect hibernate to still generate the constraint names when using auto update