NEXT documentation #1273
Merged
NEXT documentation #1273
Conversation
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
Contributor
JoelBergstrand
left a comment
JoelBergstrand
left a comment
There was a problem hiding this comment.
Great work Richard! I added som thought and edits, some which we talked about during the meeting, some that I came up with now.
modules/ROOT/pages/appendix/gql-conformance/supported-optional.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/appendix/gql-conformance/supported-optional.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
| ==== | ||
|
|
||
|
|
||
| == Interactions with conditional queries |
Contributor
There was a problem hiding this comment.
Really like this example!
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
Comment on lines
311
to
312
| [[next-and-union]] | ||
| .`NEXT` in a query using `UNION` |
Contributor
There was a problem hiding this comment.
I think this example is fine and easy to reason about, maybe not the most exciting creation ever but it does the job.
Co-authored-by: JoelBergstrand <joel.bergstrand@neo4j.com>
Collaborator
JPryce-Aklundh
left a comment
JPryce-Aklundh
left a comment
There was a problem hiding this comment.
Great work! A few editorial suggestions from me :)
Also, please add NEXT to the keywords page in this PR
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
| Even though the `NEXT` query in <<call-subquery-rewrite>> has more lines, it is divided into three segments which are easy to read. | ||
| It also avoids the parentheses and indentation of the `CALL` subquery. | ||
|
|
||
| Variables which are local to a query and which are not explicitly returned are not accessible by subsequent queries in the context of `NEXT`. This allows you to control variable scope similarly to what you can do with `WITH`, see xref:clauses/with.adoc#variable-scope[Control variables in scope]. |
Collaborator
There was a problem hiding this comment.
Should this be here?
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Jens Pryce-Åklundh <112686610+JPryce-Aklundh@users.noreply.github.com>
… with a different one that uses the example data set
Collaborator
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
neo-technology-build-agent
pushed a commit
to neo4j/neo4j
that referenced
this pull request
Jul 2, 2025
Introduces `NEXT` to Cypher which allows chaining of queries. ``` Query1 NEXT Query2 ``` [CIP 213 - NEXT statements](https://docs.google.com/document/d/1Qwi2g_yvUh9LRk4zvlRh3AH4GTzTqK2mLP2IYA5ftVI/edit?pli=1&tab=t.0#heading=h.kdb4jt9vcp34) [Docs PR](neo4j/docs-cypher#1273)
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.
No description provided.