Repository navigation
feat(database): add atomic find-and-update - #14
Merged
Merged
Conversation
Expose FindOneAndUpdate through DatabaseInterface and implement it for MongoDB. Add mock responses, queues, call tracking, reset support, and regression tests for atomic update behavior.
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
1 participant
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.
Description
Adds atomic
FindOneAndUpdatesupport to the database abstraction layer and MongoDB implementation.This change closes a gap in the current API where callers had to perform separate read and update operations, which can introduce race conditions in concurrent environments. By exposing MongoDB’s atomic find-and-update capability through
DatabaseInterface, consumers can safely update and retrieve a document in a single operation.The update also extends the mock database to fully support the new method, including:
This improves testability for components that depend on atomic update flows and keeps the mock feature set aligned with the production implementation.
Additional compile-time interface assertions were added for both
MockDatabaseandMongoClient, helping catch interface drift early during development.