docs: fix tuple-prefix range examples - #31
Open
tclinkenbeard-oai wants to merge 1 commit into
Open
Conversation
|
@tclinkenbeard-oai is attempting to deploy a commit to the panghy's projects Team on Vercel. A member of the Team first needs to authorize it. |
tclinkenbeard-oai
marked this pull request as ready for review
August 19, 2026 23:22
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.
Summary
The range examples use a packed null value as an upper bound, but null sorts before other tuple values. That excludes ordinary user keys from the examples' ranges.
Validation
No live-cluster test was run; the Java and Go examples were source-checked, not compiled or executed.