You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
bindings docs: ordered reads in 26.10.1, a projected sort key and ORDER BY ... LIMIT 1 for a bound (upstream #8811, #8812) #42
The queries guide's 'Ordered reads over an optional property' says a SQL ORDER BY p LIMIT k reads an LSM_TREE index on p in order. Measured today on upstream main 3d5e1a5 (1,000,000 records, Temurin 25 and 21): it does only when the query projects p under its own name or projects the whole record. SELECT b FROM V ORDER BY a LIMIT 5, SELECT a AS c ... ORDER BY a, and ORDER BY c (an alias of a) scan and sort, 642-806 ms against 0.4-0.9 ms; openCypher reads the index in every spelling. Filed upstream as ArcadeData#8811.
Add the condition to the paragraph, with the measured range and the workaround (project the sort property under its own name), and say Cypher is unaffected.
changed the title [-]bindings docs: SQL reads an index in order only when the sort property is projected under its own name (26.10.1, upstream #8811)[/-][+]bindings docs: ordered reads in 26.10.1, a projected sort key and ORDER BY ... LIMIT 1 for a bound (upstream #8811, #8812)[/+]on Oct 1, 2026
Activity
bindings docs: the first value past a bound through ORDER BY ... LIMI…
[-]bindings docs: SQL reads an index in order only when the sort property is projected under its own name (26.10.1, upstream #8811)[/-][+]bindings docs: ordered reads in 26.10.1, a projected sort key and ORDER BY ... LIMIT 1 for a bound (upstream #8811, #8812)[/+]bindings docs: ordered reads, project the sort property under its own…
benchmarks: the instrument changes for the 26.10.1 re-pin campaign, w…