HHH-19565 @SQLRestriction should not be applied to a @ManyToOne #10381
+899
−656
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gavinking
changed the title
At least not when mapped to a foreign key association. If we apply such a restriction, we will set the FK to null when the entity is updated, resulting in data loss. Note that this was the historical and correct behavior right up until Hibernate 6.2. Some recent tests are asserting a different and dangerous behavior, so I'm changing those tests.
…able In this case, we won't set the FK to null. Instead, we can handle it with an upsert (SQL MERGE).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts to the behavior prior to H6.2, where
@Wherea.k.a.@SQLRestrictiondid not affect@OneToManyassociation fetching.This change continues to add the restriction when:
@OneToManyis mapped to a@JoinTable, or@OneToOnemapped to a FK.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-19565