feat(database): add explicit atomic single-record mutations - #15
Merged
Merged
Conversation
This was referenced Sep 14, 2026
Upd4ting
marked this pull request as ready for review
September 14, 2026 16:10
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
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.
Contract
Adds a direct instance-scoped Table.atomicMutation primitive for revision-checked constant patch/delete and narrowly scoped scalar-equality deletion. Conditions belong inside the native target mutation; generic filtered writes do not satisfy this contract. MissingRevision is absent-field-only, never null or absent record. Unknown acknowledgements never become mismatch or trigger automatic retry.
Verification
Draft prerequisite
Keep draft until compatible adapters and the consumer graph are verified. Version remains 0.1.4 and is not published. PostgreSQL declared columns cannot distinguish absent revision from null; missing bootstrap requires supported overflow storage or explicit rejection. No merge, release, deployment, or shared-data migration is authorized by this PR.