Skip to content

HHH-19640 generated fields and forced version increments #10624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 25, 2025

Conversation

gavinking
Copy link
Member

@gavinking gavinking commented Jul 24, 2025

When an entity has on-execution generated fields, we have to include them in the UPDATE statement even for a "forced" version increment. So we must skip an optimization.

[Please describe here what your change is about]


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.


https://hibernate.atlassian.net/browse/HHH-19640

When an entity has fields generated on update, we have to include
them in the UPDATE statement even for a "forced" version increment.
So we must skip an optimization.
@gavinking gavinking marked this pull request as ready for review July 25, 2025 00:32
@gavinking gavinking changed the title HHH-19640 on-execution generated fields and forced version increments HHH-19640 generated fields and forced version increments Jul 25, 2025
@gavinking
Copy link
Member Author

The failure on HSQLDB is unrelated.

@gavinking gavinking merged commit 2e9eac2 into hibernate:main Jul 25, 2025
22 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant