Repository navigation
Cover NEXT, WHEN, COLLECT and the other 3.0.2 features in depth - #21
Merged
Merged
Conversation
Gives NEXT and WHEN their own page (query/composition), and extends the examples for the other new features, each checked on a 3.0.2 server: - NEXT: passing nodes on, longer chains, after a UNION, braced chains as UNION sides, inside CALL / EXISTS / COUNT, writes, scoping rules; - WHEN: several branches, subquery conditions, per row after NEXT and in CALL, no ELSE, NEXT chains in a branch, UNION, writes, rules; - COLLECT: WHERE, DISTINCT, top-k, UNION, collected nodes, use in WHERE / UNWIND / SET, and its limits; UNION bodies for EXISTS/COUNT; CALL bodies that write and return; - FOREACH: edges off a matched node, several clauses, list properties, conditional writes, RETURN after it; - parameters: label expressions, WHERE tests, $0, MERGE, errors; - functions: string, normalize, conversion and aggregate examples; label expressions in OPTIONAL MATCH and WHERE NOT; quantified-path group variables; ASCENDING / DESCENDING.
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.
Follow-up to #20. Its second commit was pushed a moment after #20 was merged, so it never reached
main. This PR is that commit, cherry-picked ontomainunchanged.What
New page, NEXT and WHEN (
query/composition, in the nav after Results and aggregation). The NEXT and WHEN sections move there from Results and aggregation.NEXT: passing nodes to the next step, longer chains, after aUNION, braced chains asUNIONsides, insideCALL/EXISTS/COUNT, writes, and the scoping and alias rules.WHEN ... THEN ... ELSE: several branches, subquery conditions (WHEN EXISTS {...},WHEN COUNT {...} > 3), per row afterNEXTand inCALL, behaviour withoutELSE,NEXTchains in a branch,UNION, writes, and rules.More examples on existing pages
COLLECT { }:WHERE,DISTINCT, top-k withORDER BY/LIMIT,UNION, collected nodesWHERE/UNWIND/SETNEXTorWHENinsideUNIONbodies forEXISTSandCOUNT, andCALLbodies that write and return what they wrote.FOREACH: edges off a matched node, several clauses per element, list properties (converted withtoString), conditional writes with theCASEtrick,RETURNafter it.WHERE n:$label, numbered$0,MERGElabels and edge types, and both error messages.normalize, conversion and statistical functionsOPTIONAL MATCHandWHERE NOTUNWIND/ORDER BYASCENDING/DESCENDINGHow it was checked
cypherexample inquery/(332 statements) was run against a 3.0.2 server, on the sample graph from the matching page.my_index,knows.csv, thegreeterextension, two multi-command blocks).NEXT,WHENandCOLLECTaccept and reject, and the exact error messages.npm run buildpasses (43 pages), and every new internal link resolves.