support for OPTIMISTIC + OPTIMISTIC_FORCE_INCREMENT LockModes #329
Conversation
This file contains 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
Closed
These LockModes force a version check or upgrade right at the end of the transaction. This required building infrastructure for reactive before/after transaction completion events. Fixes hibernate#201
Also big cleanup to related code, and a couple of minor bugfixes to implementation of lock() operation. Also tests. For hibernate#329
gavinking
added a commit
that referenced
this pull request
Aug 24, 2020
(Forgot to update the Javadoc.) For #329
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.
These
LockModes force a version check or upgrade right at the end of the transaction.This required building infrastructure for reactive before/after transaction completion events.
Fixes #201
Still TODO: support passing
OPTIMISTIC,OPTIMISTIC_FORCE_INCREMENTtosession.lock()