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
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.
Part of the document-owned attachment implementation requested by Upd4ting: https://github.com/AntelopeJS/cms/pull/374.
Implements optional database transactions with session propagation, rollback, bounded commit acknowledgement, no callback replay, and rejection of nested or detached database work. Document persistence and registry ownership claims share one atomic transaction.
Verification: 179 tests pass against a disposable MongoDB replica set. CMS additionally passes 27 real HTTP/storage/database attachment tests, including concurrent claims and rollback.
Requires the new interface-database transactions entrypoint. Tested with a local packed interface; clean registry installation is blocked until its release and the provider dependency floor/lockfile update. Requires a replica set or sharded topology, not standalone MongoDB. No deployment or package publication is included.
This transaction approach does not depend on the earlier atomic-single-record proposal (#33).