Skip to content

Commit 0e6ef95

Browse files
l-heemannLojjs
authored andcommitted
Review comments
1 parent 693d69a commit 0e6ef95

File tree

2 files changed

+9
-8
lines changed

2 files changed

+9
-8
lines changed

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

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -229,14 +229,14 @@ Dots in alias names are ambiguous.
229229
They could either be interpreted as part of the name itself, or as the dot that separates a composite namespace from the alias name.
230230

231231
=== Conflicting names
232-
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`.
232+
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`.
233233
Both of these would be referred to by the same name `garden.flowers`.
234234

235-
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.
235+
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.
236236

237237
[.tabbed-example]
238238
=====
239-
[role=include-with-cypher-5]
239+
[role=include-with-cypher-5 label--new-2025.06]
240240
======
241241
Creating a regular alias with the same name as an existing composite constituent is disallowed:
242242

@@ -331,7 +331,7 @@ Creating a composite constituent with the same name as an existing non-composite
331331

332332
Cypher 25 relies on the guarantee that no conflicting names are allowed in Neo4j 2025.06 and later.
333333
The following queries all act on the same alias, regardless if that alias is a composite constituent or not.
334-
The special quoting of separate name parts that was necessary in Cypher 5 is not necessary / permitted in Cypher 25.
334+
The special quoting of separate name parts that was necessary in Cypher 5 is not permitted in Cypher 25.
335335

336336
.Parameters
337337
[source, javascript]
@@ -349,7 +349,7 @@ CYPHER 25 USE `my.garden.beautiful.flowers` RETURN 1
349349
----
350350

351351
==== Creating a new alias with dots
352-
During `CREATE`, Cypher25 will split the given name on each dot, left to right, and check if a corresponding composite database exists.
352+
During `CREATE`, Cypher 25 will split the given name on each dot, left to right, and check if a corresponding composite database exists.
353353
If no composite database is found, Cypher25 will fall back to creating a regular non-composite alias instead.
354354

355355
The following query attempts to create in order:
@@ -375,6 +375,7 @@ Since it finds the composite database `my.garden` it will create the constituent
375375

376376
The composite database name and the database alias name need to be quoted individually.
377377
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`++`.
378+
Note however that separating composite database name and alias name with backticks is no longer supported in Cypher 25.
378379

379380
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`:
380381

@@ -418,9 +419,9 @@ CYPHER 5 CREATE ALIAS `my.alias.with.dots` FOR DATABASE `northwind-graph`
418419
CYPHER 5 CREATE ALIAS `my.composite.database.with.dots`.`my.other.alias.with.dots` FOR DATABASE `northwind-graph`
419420
----
420421

421-
422-
[role=label--deprecated]
423422
==== Single dots and local database aliases
423+
[NOTE]
424+
This used to be deprecated, but the deprecation has since been revoked.
424425

425426
There is a special case for local database aliases with a single dot without any existing composite database.
426427
If a composite database `some` exists, the query below will create a database alias named `alias` within the composite database `some`.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,5 +21,5 @@ The name restrictions and escaping rules apply to all the different database ali
2121
====
2222
Having dots (`.`) in the database alias names is not recommended.
2323
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].
2525
====

0 commit comments

Comments
 (0)