-
Notifications
You must be signed in to change notification settings - Fork 64
add graph reference section to expressions #1162
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
+66
−12
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
524f4db
add graph reference section to expressions
nadja-muller 81a695c
Apply suggestions from code review
nadja-muller c7dc2e0
Update modules/ROOT/pages/queries/expressions.adoc
nadja-muller aab9b59
merge lists
nadja-muller c3da911
add deprecation for graph function string arguments
nadja-muller 2bccaa4
formatting
nadja-muller bef6e03
fixing wrong/improving descriptions
nadja-muller ef6af69
Apply suggestions from code review
nadja-muller 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -82,3 +82,21 @@ String literals can contain the following escape sequences: | |
| * A predicate expression (i.e. an expression returning a `BOOLEAN` value): `a.prop = 'Hello'`, `length(p) > 10`, `a.name IS NOT NULL`. | ||
| * Label and relationship type expressions: `(n:A|B)`, `+()-[r:R1|R2]->()+`. | ||
| * `null`. | ||
|
|
||
| [[graphreferences]] | ||
nadja-muller marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| == Graph references | ||
| * static graph references: `USE <symbolic-name>` (for standard and system databases), `USE <symbolic-name>.<symbolic-name>` (for composite databases) | ||
| * dynamic graph reference with the xref:functions/graph.adoc#functions-graph-byname[`graph.byName`] function, to access a graph of a given name: `USE graph.byName(<string-expression>)` | ||
| * dynamic graph reference with the xref:functions/graph.adoc#functions-graph-by-elementid[`graph.byElementId`] function, to access a graph of a given node or relationship: `USE graph.byName(<element-id-string>)` | ||
nadja-muller marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| Rules on string expressions for graph references when using identifiers (static graph references, administration commands) or a string (graph.byName function): | ||
|
|
||
| * Unquoted dots are separators between a composite database and its constituent. For example, `composite.db1` represents the constituent composite.db1 in the composite database composite. To refer to a database with a dot in its name, quote the graph reference instead: `+`composite.db1`+` | ||
nadja-muller marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| * When resolving a graph reference within a graph function, the string argument is parsed the same as a static graph reference before resolving it. This means that for most arguments, `USE graph.byName(<graph-reference>)` is equal to `USE <graph-reference>`. However, escaping rules for xref::syntax/naming.adoc#symbolic-names-escaping-rules[symbolic names] are applied to the argument. When passing in a string literal, this means both the escaping rules for xref:queries/expressions.adoc#expressions-string-literals[string literals] (when parsing the query) as well as the escaping rules for xref::syntax/naming.adoc#symbolic-names-escaping-rules[symbolic names] (when evaluating the graph reference) are applied. For example, the graph reference in `USE graph.byName('+composite.1\\u0041+')` will resolve to the constituent `composite.1a` of the composite database `composite`. | ||
nadja-muller marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| Graph references are used within: | ||
|
|
||
| * xref:clauses/use.adoc[`USE clauses`] | ||
| * database and alias names when managing databases and aliases, see link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/[Database administration] | ||
|
||
|
|
||
|
|
||
Oops, something went wrong.
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.