Repository navigation
Support static keyset reads over composite primary keys - #186
Merged
Merged
Conversation
1 of 2 tasks
added 9 commits
October 23, 2026 17:37
first-assist
force-pushed
the
platform/composite-keyset-r5
branch
from
October 23, 2026 06:39
ec58025 to
dbb82f2
Compare
first-assist
marked this pull request as ready for review
October 23, 2026 07:34
This was referenced Oct 23, 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
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.
Configured keysets and authorized scans support composite primary keys. The declared order ends with every key component in declaration order, rejects repeated columns and retains typed values through nullable ordering, forward/backward windows and cursor identity.
Every configured ordering field and complete key component requires current authority before SQL and before releasing cursors or scan metadata, even for cursor-only selections. Explicit repository surface flags cannot publish a private GraphQL cursor field; repository policy remains independent.
Owned SQLite regressions cover tuple collisions, nullable ordering, reverse traversal, generated read surfaces and zero-SELECT rejection for denied cursor fields. The exact two indentation suggestions from hosted job 120200514199 are applied without changing assertions or runtime code. No local formatter or Rust command ran; current-head CI/backend/Clippy/Rustdoc qualification remains pending. Keep draft; Root alone merges.
After #187 merged at 5c860fc, this branch was rebased onto that exact main commit. The paired ORM/macros capability advances to 0.59.0. All seven workspace/fixture lockfiles change only those two local package versions; external package records are unchanged. The generated workspace inventory changes only the matching two version cells pending confirmation by fresh hosted Cargo metadata. Documentation (210), package release policy and diff checks pass. Prior green CI applied to ec58025 and does not qualify this new head; fresh CI is pending Root relay. No local Rust/Cargo/fmt command ran during the a17 blackout.
Documentation impact
Current source:
dbb82f29c5f5b99bb19489d99a61addbbe531b15(tree17a9f5c35f8faa1f01e3af35d8adab9c37e6120d).