You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -223,14 +223,14 @@ Dots in alias names are ambiguous.
223
223
They could either be interpreted as part of the name itself, or as the dot that separates a composite namespace from the alias name.
224
224
225
225
=== Conflicting names
226
-
Before Neo4j 2025.06 it was possible to create conflicting aliases such as the constituent alias `flowers` within the composite database `garden` as well as the non-composite local alias `garden.flowers`.
226
+
Before Neo4j 2025.06, it was possible to create conflicting aliases such as the constituent alias `flowers` within the composite database `garden` as well as the non-composite local alias `garden.flowers`.
227
227
Both of these would be referred to by the same name `garden.flowers`.
228
228
229
-
Neo4j 2025.06 ensures that no such conflicts exist and will throw an exception when attempting to create a new alias with the same name as an existing alias.
229
+
Neo4j 2025.06 and later versions ensure that no such conflicts exist and will throw an exception when attempting to create a new alias with the same name as an existing alias.
230
230
231
231
[.tabbed-example]
232
232
=====
233
-
[role=include-with-cypher-5]
233
+
[role=include-with-cypher-5 label--new-2025.06]
234
234
======
235
235
Creating a regular alias with the same name as an existing composite constituent is disallowed:
236
236
@@ -325,7 +325,7 @@ Creating a composite constituent with the same name as an existing non-composite
325
325
326
326
Cypher 25 relies on the guarantee that no conflicting names are allowed in Neo4j 2025.06 and later.
327
327
The following queries all act on the same alias, regardless if that alias is a composite constituent or not.
328
-
The special quoting of separate name parts that was necessary in Cypher 5 is not necessary / permitted in Cypher 25.
328
+
The special quoting of separate name parts that was necessary in Cypher 5 is not permitted in Cypher 25.
329
329
330
330
.Parameters
331
331
[source, javascript]
@@ -343,7 +343,7 @@ CYPHER 25 USE `my.garden.beautiful.flowers` RETURN 1
343
343
----
344
344
345
345
==== Creating a new alias with dots
346
-
During `CREATE`, Cypher25 will split the given name on each dot, left to right, and check if a corresponding composite database exists.
346
+
During `CREATE`, Cypher 25 will split the given name on each dot, left to right, and check if a corresponding composite database exists.
347
347
If no composite database is found, Cypher25 will fall back to creating a regular non-composite alias instead.
348
348
349
349
The following query attempts to create in order:
@@ -369,6 +369,7 @@ Since it finds the composite database `my.garden` it will create the constituent
369
369
370
370
The composite database name and the database alias name need to be quoted individually.
371
371
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`++`.
372
+
Note however that separating composite database name and alias name with backticks is no longer supported in Cypher 25.
372
373
373
374
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`:
374
375
@@ -412,9 +413,9 @@ CYPHER 5 CREATE ALIAS `my.alias.with.dots` FOR DATABASE `northwind-graph`
412
413
CYPHER 5 CREATE ALIAS `my.composite.database.with.dots`.`my.other.alias.with.dots` FOR DATABASE `northwind-graph`
413
414
----
414
415
415
-
416
-
[role=label--deprecated]
417
416
==== Single dots and local database aliases
417
+
[NOTE]
418
+
This used to be deprecated, but the deprecation has since been revoked.
418
419
419
420
There is a special case for local database aliases with a single dot without any existing composite database.
420
421
If a composite database `some` exists, the query below will create a database alias named `alias` within the composite database `some`.
Copy file name to clipboardExpand all lines: modules/ROOT/pages/database-administration/aliases/naming-aliases.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,5 +21,5 @@ The name restrictions and escaping rules apply to all the different database ali
21
21
====
22
22
Having dots (`.`) in the database alias names is not recommended.
23
23
This is due to the difficulty of determining if a dot is part of the database alias name or a delimiter for a database alias in a composite database.
24
-
For more details, see xref:database-administration/aliases/manage-aliases-composite-databases.adoc#alias-management-escaping[names and escaping for database aliases targeting composite databases].
24
+
For more details, see xref:database-administration/aliases/manage-aliases-composite-databases.adoc#alias-management-escaping[database alias names that contain dots].
0 commit comments