Repository navigation
Route Python SQL writes through context-owned Internal ID allocator - #58
Merged
Merged
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.
Tracks #56; keep the issue open until the immutable internal artifact consumer gate completes. Typed async InternalIdAllocator registration on UserContext rejects malformed or synchronous installations. Direct INSERT, nested batch, explicit-ID floor, and graph Save use the installed allocator; SQL provider default applies only without an override. Includes SQLite positive/negative/concurrency tests, a runnable local-source example, and documentation. Local verification: 854 passed, 8 skipped; full examples gate PASS against a dedicated local S3 fixture; dedicated Internal ID example passed twice. Public release/generator adoption are out of scope.