-
Notifications
You must be signed in to change notification settings - Fork 64
Add ALL keyword to RETURN clause as part of GQL compliance #1139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
JPryce-Aklundh
merged 2 commits into
neo4j:cypher-25
from
gem-neo4j:cypher25_add_all_keyword_to_return
Apr 11, 2025
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -234,3 +234,56 @@ As the limit is larger than the total number of remaining rows, all rows are ret | |
| | 6 | ||
| |Rows: 4 | ||
| |=== | ||
|
|
||
| [[with-unique-results]] | ||
| == Unique results | ||
|
|
||
| `DISTINCT` retrieves only unique rows for the columns that have been selected for projection. | ||
|
|
||
| .Query | ||
| [source, cypher] | ||
| ---- | ||
| MATCH (n)-[:KNOWS]->(p) | ||
| WITH DISTINCT p.name AS name | ||
| RETURN name | ||
| ---- | ||
|
|
||
| `'George'` is returned by the query, but only once (without the `DISTINCT` operator it would have been returned twice because there are two `KNOWS` relationships going to it): | ||
|
|
||
| .Result | ||
| [role="queryresult",options="header,footer",cols="1*<m"] | ||
| |=== | ||
| | name | ||
| | "Bossman" | ||
| | "George" | ||
| | "Anders" | ||
| d|Rows: 3 | ||
| |=== | ||
|
|
||
|
|
||
| [[with-all-results]] | ||
| == WITH ALL | ||
|
|
||
| Projecting all results can also be accomplished by explicitly including `ALL` in the `WITH`. | ||
|
|
||
|
Comment on lines
+264
to
+268
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It isn't introduced for GQL compliance, WITH doesn't exist in GQL, it was introduced for consistency
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah yes, sorry! |
||
| .Query | ||
| [source, cypher] | ||
| ---- | ||
| MATCH (n)-[:KNOWS]->(p) | ||
| WITH ALL p.name AS name | ||
| RETURN name | ||
| ---- | ||
|
|
||
| The same name is returned twice, as there are two `KNOWS` relationships connecting to it. | ||
|
|
||
| .Result | ||
| [role="queryresult",options="header,footer",cols="1*<m"] | ||
| |=== | ||
| | name | ||
| | "Bossman" | ||
| | "George" | ||
| | "George" | ||
| | "Anders" | ||
| d|Rows: 4 | ||
| |=== | ||
|
|
||
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
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.
Uh oh!
There was an error while loading. Please reload this page.