This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
bindings docs: ordered reads need MANDATORY with NOTNULL, and Cypher reads the index in order only ascending (#26) - #27
Merged
Conversation
…reads the index in order only ascending (#26) NOTNULL rejects an explicit null but not a record that leaves the property out, which has no index key either (ArcadeData#8701), so the ordered-reads advice names MANDATORY and NOTNULL together. The descending sentence is scoped to SQL, and a paragraph gives the openCypher behavior measured on the 26.10.1 snapshot (ArcadeData#8724) with the range workaround. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WWcDr7TwvcfMsQkeYQVHZr
This was referenced Sep 30, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #26.
docs/guide/core/queries.md, "Ordered reads over an optional property":MANDATORYandNOTNULLtogether.NOTNULLalone rejects an explicit null but not a record that leaves the property out, which has no index key either (Regression: the new NOTNULL fast path for an index-ordered ORDER BY drops every record that simply does not have the property, because NOTNULL does not make a property mandatory ArcadeData/arcadedb#8701); the example now declares(mandatory true, notnull true).2fa02b3dde(openCypher: ORDER BY an indexed property LIMIT k scans the whole label when descending on a MANDATORY NOTNULL property, under WHERE x IS NOT NULL, and with a NULL_STRATEGY INDEX index in either direction (850-1,130 ms against 0.5-1.7 ms at 1M vertices) ArcadeData/arcadedb#8724): index order over a whole label only for an ascendingORDER BY n.p LIMIT kwith noWHEREon a default-null-strategy index; a descending read,WHERE n.p IS NOT NULL, or aNULL_STRATEGY INDEXindex scans the label; a range predicate is served in either direction.Checked:
mkdocs build --strictpasses. Docs only; no code, test, or example changes (the only other NOTNULL declaration in the docs,api/schema.md, already pairs it withmandatory).🤖 Generated with Claude Code
https://claude.ai/code/session_01WWcDr7TwvcfMsQkeYQVHZr