Add optimistic locking - #11
Merged
Merged
Conversation
DavidBadura
force-pushed
the
optimistic-locking
branch
from
August 29, 2026 08:41
466a664 to
7c62dac
Compare
DanielBadura
approved these changes
Aug 31, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Mark an int property with
#[Version]to guardupdate()against concurrent writes. The repository adds the loaded version to the update filter, bumps it, and throws OptimisticLockFailed when no document matched. On success the new version is written back onto the object so workers can keep updating the same instance.Works the same on MongoDB and Rango. The version property must not be readonly because of the write-back & a second #[Version] or a readonly one fails when the metadata is built.