Skip to content
This repository was archived by the owner on Nov 21, 2026. It is now read-only.

bindings docs: ordered reads need MANDATORY with NOTNULL, and Cypher reads the index in order only ascending (#26) - #27

Merged
tae898 merged 1 commit into
mainfrom
docs-ordered-reads-mandatory-cypher
Sep 30, 2026
Merged

tae898 merged 1 commit into
mainfrom
docs-ordered-reads-mandatory-cypher

Conversation

@tae898

@tae898 tae898 commented Sep 30, 2026

Copy link
Copy Markdown

Closes #26.

docs/guide/core/queries.md, "Ordered reads over an optional property":

Checked: mkdocs build --strict passes. Docs only; no code, test, or example changes (the only other NOTNULL declaration in the docs, api/schema.md, already pairs it with mandatory).

🤖 Generated with Claude Code

https://claude.ai/code/session_01WWcDr7TwvcfMsQkeYQVHZr

…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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bindings docs: ordered reads need MANDATORY with NOTNULL (ArcadeDB #8701), and Cypher reads the index in order only ascending (ArcadeDB #8724)

1 participant