Skip to content

Commit 78deb56

Browse files
committed
found more mentions of escape when referring backticks
1 parent 41adb6a commit 78deb56

File tree

4 files changed

+13
-13
lines changed

4 files changed

+13
-13
lines changed

modules/ROOT/pages/authentication-authorization/dbms-administration.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2069,9 +2069,9 @@ In this case, `+*+` means 0 or more characters, and `?` matches exactly one char
20692069
====
20702070
The name-globbing is subject to the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/syntax/naming/[Cypher Manual -> Naming rules and recommendations], with the exception that it may include dots, stars, and question marks without the need for escaping using backticks.
20712071
2072-
Each part of the name-globbing separated by dots may be individually escaped.
2072+
Each part of the name-globbing separated by dots may be individually quoted.
20732073
For example, `++mine.`procedureWith%`++` is allowed, but not `++mine.procedure`With%`++`.
2074-
Also, note that wildcard characters behave as wildcards even when escaped.
2074+
Also, note that wildcard characters behave as wildcards even when quoted.
20752075
For example, using `++`*`++` is equivalent to using `+*+`, and thus allows executing all functions or procedures and not only the procedure or function named `+*+`.
20762076
====
20772077

@@ -2134,7 +2134,7 @@ Users with the role `globbing6` can run procedures `mine.public.with#Special§Ch
21342134

21352135
[NOTE]
21362136
====
2137-
The name-globbing may be fully or partially escaped.
2137+
The name-globbing may be fully or partially quoted.
21382138
Both `+*+` and `+?+` are interpreted as wildcards in both cases.
21392139
====
21402140

modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -216,9 +216,9 @@ SHOW DATABASE garden YIELD name, type, constituents
216216
Naming database aliases in composite databases follows the same rule as xref:database-administration/aliases/naming-aliases.adoc[naming aliases for standard databases].
217217
However, when it comes to escaping names using backticks, there are some additional things to consider:
218218

219-
=== Escaping database alias and composite database names
219+
=== Quoting database alias and composite database names
220220

221-
The composite database name and the database alias name need to be escaped individually.
221+
The composite database name and the database alias name need to be quoted individually.
222222
Backticks may be added regardless of whether the name contains special characters or not, so it is good practice to always backtick both names, e.g. `++`composite`++.++`alias`++`.
223223

224224
The following example creates a database alias named `my alias with spaces` as a constituent in the composite database named `my-composite-database-with-dashes`:
@@ -236,7 +236,7 @@ CREATE DATABASE `northwind-graph`;
236236
CREATE ALIAS `my-composite-database-with-dashes`.`my alias with spaces` FOR DATABASE `northwind-graph`
237237
----
238238

239-
When not escaped individually, a database alias with the full name `my alias with.dots and spaces` gets created instead:
239+
When not quoted individually, a database alias with the full name `my alias with.dots and spaces` gets created instead:
240240

241241
.Query
242242
[source, cypher]
@@ -249,7 +249,7 @@ CREATE ALIAS `my alias with.dots and spaces` FOR DATABASE `northwind-graph`
249249
//Examples where dots are not separators between composite name and alias name are impossible to test, because the right escaping cannot be inferred automatically.
250250

251251
Database alias names may also include dots.
252-
Though these always need to be escaped in order to avoid ambiguity with the composite database and database alias split character.
252+
Though these always need to be quoted in order to avoid ambiguity with the composite database and database alias split character.
253253

254254
.Query
255255
[source, cypher, role=test-skip]
@@ -279,7 +279,7 @@ CREATE ALIAS some.alias FOR DATABASE `northwind-graph`
279279

280280
=== Handling parameters
281281

282-
When using parameters, names cannot be escaped.
282+
When using parameters, names cannot be quoted.
283283
When the given parameter includes dots, the first dot will be considered the divider for the composite database.
284284

285285
Consider the query with parameter:
@@ -315,7 +315,7 @@ Consider the same query but with the following parameter:
315315
Since the first dot will be used as a divider, the command will attempt to create the database alias `withdot.myalias` in the composite database `mycompositedatabase`.
316316
If `mycompositedatabase` does not exist, the command will create a database alias with the name `mycompositedatabase.withdot.myalias`, which is not part of any composite database.
317317

318-
In these cases, it is recommended to avoid parameters and explicitly escape the composite database name and alias name separately to avoid ambiguity.
318+
In these cases, it is recommended to avoid parameters and explicitly quote the composite database name and alias name separately to avoid ambiguity.
319319

320320
=== Handling parameters
321321

@@ -356,4 +356,4 @@ Failed to delete the specified database alias 'foo.bar': Database alias does not
356356

357357
Had the composite database `foo` not existed, the database alias `foo.bar` would have been dropped.
358358

359-
In these cases, it is recommended to avoid parameters and explicitly escape the composite database name and alias name separately to avoid ambiguity.
359+
In these cases, it is recommended to avoid parameters and explicitly quote the composite database name and alias name separately to avoid ambiguity.

modules/ROOT/pages/database-administration/aliases/naming-aliases.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ The following naming rules apply:
1010
* A name is a valid identifier.
1111
* Name length can be up to 65534 characters.
1212
* Names cannot end with dots.
13-
* Unescaped dots signify that the database alias belongs to a composite database, separating the composite database name and the alias name.
13+
* Unquoted dots signify that the database alias belongs to a composite database, separating the composite database name and the alias name.
1414
* Names that begin with an underscore or with the prefix `system` are reserved for internal use.
15-
* Non-alphabetic characters, including numbers, symbols, dots, and whitespace characters, can be used in names, but must be escaped using backticks.
15+
* Non-alphabetic characters, including numbers, symbols, dots, and whitespace characters, can be used in names, but must be quoted using backticks.
1616
1717
The name restrictions and escaping rules apply to all the different database alias commands.
1818

modules/ROOT/pages/database-administration/standard-databases/naming-databases.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Naming rules for databases are as follows:
1919
The `-` (dash) and `.` (dot) characters are not legal in Cypher variables.
2020
Names with a `-` in them must be enclosed within backticks.
2121
For example, `CREATE DATABASE ++`main-db`++` is a valid database name.
22-
Database names are the only identifier for which dots do not need to be escaped.
22+
Database names are the only identifier for which dots do not need to be quoted.
2323
For example `main.db` is a valid database name.
2424
However, this behavior is deprecated due to the difficulty of determining if a dot is part of the database name or a delimiter for a database alias in a composite database.
2525
====

0 commit comments

Comments
 (0)