Clauses and subclauses #1272
Draft
Clauses and subclauses #1272
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
rsill-neo4j
reviewed
May 8, 2025
|
|
||
| [[query-order]] | ||
| = ORDER BY | ||
|
|
||
| `ORDER BY` specifies how the output of a clause should be sorted. | ||
| It be used as a sub-clause following `RETURN` or `WITH`. | ||
| It be used as a subclause following `RETURN` or `WITH`. |
There was a problem hiding this comment.
Suggested change
| It be used as a subclause following `RETURN` or `WITH`. | |
| It is used as a subclause following `RETURN` or `WITH`. |
Comment on lines
277
to
281
| RETURN COLLECT { | ||
| MATCH (person)-[:HAS_DOG]->(d:Dog) | ||
| RETURN d.name } AS dogNames, | ||
| avg(person.age) AS averageAge | ||
| ORDER BY dogNames |
There was a problem hiding this comment.
Suggested change
| RETURN COLLECT { | |
| MATCH (person)-[:HAS_DOG]->(d:Dog) | |
| RETURN d.name } AS dogNames, | |
| avg(person.age) AS averageAge | |
| ORDER BY dogNames | |
| RETURN COLLECT { | |
| MATCH (person)-[:HAS_DOG]->(d:Dog) | |
| RETURN d.name | |
| } AS dogNames, | |
| avg(person.age) AS averageAge | |
| ORDER BY dogNames |
There was a problem hiding this comment.
the ending curly was very hard to spot
| MATCH (person)-[:HAS_DOG]->(:Dog) | ||
| RETURN person.name AS name, | ||
| EXISTS { | ||
| MATCH (person)-[:HAS_DOG]->(:Dog) | ||
| } AS hasDog |
There was a problem hiding this comment.
Suggested change
| } AS hasDog | |
| } AS hasDog |
There was a problem hiding this comment.
not sure about the correct amount of spaces, but i think this should be at the same level of the E from EXISTS, letting the curly end nicely
rsill-neo4j
reviewed
May 20, 2025
| = Graph selection clauses | ||
| :description: Information about Cypher's graph selection clauses. | ||
|
|
||
| Cypher's contains one graph selection clause -- `USE` -- which allows you to select which graph a query, or query part, is executed against. |
There was a problem hiding this comment.
Suggested change
| Cypher's contains one graph selection clause -- `USE` -- which allows you to select which graph a query, or query part, is executed against. | |
| Cypher contains one graph selection clause -- `USE` -- which allows you to select which graph a query, or query part, is executed against. |
i'd say it's preference, but maybe "a" (or even "a single") instead of "one"?
| = Import clauses | ||
| :description: Information about Cypher's import clauses. | ||
|
|
||
| Cypher's contains one clause to import data -- `LOAD CSV` -- which allows you to load csv into a graph. |
There was a problem hiding this comment.
Suggested change
| Cypher's contains one clause to import data -- `LOAD CSV` -- which allows you to load csv into a graph. | |
| Cypher contains one clause to import data -- `LOAD CSV` -- which allows you to load csv into a graph. |
same here (a vs a single vs one)
| @@ -3,291 +3,26 @@ | |||
| [[query-clause]] | |||
| = Clauses | |||
|
|
|||
| This section contains information on all the clauses in the Cypher query language. | |||
| This chapter contains information on all the clauses and subclauses in the Cypher query language (with the exception of the database administration commands, which are documented in the link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/[Operations Manual -> Database administration], link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/[Authentication and authorization], and link:{neo4j-docs-base-uri}/operations-manual/current/clustering/[Clustering]). | |||
There was a problem hiding this comment.
style preference - i'd drop the parentheses
|
This PR includes documentation updates New pages:
Updated pages: |
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.