Bug: save with cascade of @OneToOne + @Version model sets version to 1 #2558
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.
When saving a model, that contains a @OnetoOne Model with @Version, the child models' version will be set to 1.
Then, when the child model will be saved, a OptimisticLockException occures due to the wrong version.
(see test)
Furthermore the 'child'-model also has to have a xToMany-Relation to another model, so that the flag 'saveRecurseSkippable' in BeanPropertyAssoc is set to false.