Update the Handling parameters section (#3132)

Author: renetapopova

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

@@ -328,8 +328,6 @@ The exception has GQLSTATUS code link:{neo4j-docs-base-uri}/status-codes/current
 ======
 =====
 
-
-
 [role=label--new-2025.06]
 === Cypher 25 specific behaviour
 ==== Accessing an existing alias with dots
@@ -376,8 +374,6 @@ The query attempts to create the following aliases in the given order:
 
 When it finds the composite database `my.garden`, it creates the constituent alias `beautiful.flowers` within that composite.
 
-
-
 === Cypher 5 specific behaviour
 
 ==== Quoting database alias and composite database names
@@ -402,15 +398,15 @@ CREATE DATABASE `northwind-graph`;
 .Query
 [source, cypher]
 ----
-CYPHER 5 CREATE ALIAS `my-composite-database-with-dashes`.`my alias with spaces` FOR DATABASE `northwind-graph`
+CYPHER 5 CREATE ALIAS `my-composite-database-with-dashes`.`my alias with spaces` FOR DATABASE `northwind-graph`;
 ----
 
 When not quoted individually, a database alias with the full name `my alias with.dots and spaces` gets created instead:
 
 .Query
 [source, cypher]
 ----
-CYPHER 5 CREATE ALIAS `my alias with.dots and spaces` FOR DATABASE `northwind-graph`
+CYPHER 5 CREATE ALIAS `my alias with.dots and spaces` FOR DATABASE `northwind-graph`;
 ----
 
 ==== Handling multiple dots
@@ -423,13 +419,13 @@ Though these always need to be quoted in order to avoid ambiguity with the compo
 .Query
 [source, cypher, role=test-skip]
 ----
-CYPHER 5 CREATE ALIAS `my.alias.with.dots` FOR DATABASE `northwind-graph`
+CYPHER 5 CREATE ALIAS `my.alias.with.dots` FOR DATABASE `northwind-graph`;
 ----
 
 .Query
 [source, cypher, role=test-skip]
 ----
-CYPHER 5 CREATE ALIAS `my.composite.database.with.dots`.`my.other.alias.with.dots` FOR DATABASE `northwind-graph`
+CYPHER 5 CREATE ALIAS `my.composite.database.with.dots`.`my.other.alias.with.dots` FOR DATABASE `northwind-graph`;
 ----
 
 ==== Single dots and local database aliases
@@ -445,13 +441,19 @@ If no such database exists, however, the same query will instead create a databa
 .Query
 [source, cypher]
 ----
-CYPHER 5 CREATE ALIAS some.alias FOR DATABASE `northwind-graph`
+CYPHER 5 CREATE ALIAS some.alias FOR DATABASE `northwind-graph`;
 ----
 
 ==== Handling parameters
 
+When using parameters to specify database alias names, the same rules apply as when using literal strings.
+However, since parameters cannot be quoted, it is not possible to specify the composite database name and the alias name separately when using parameters.
+This means that the first dot in the parameter value will always be considered as the separator between the composite database name and the alias name, which can lead to unexpected results if the parameter value contains dots.
+
+===== Parameters with dots
+
 When using parameters, names cannot be quoted.
-When the given parameter includes dots, the first dot will be considered the divider for the composite database.
+When the given parameter includes dots, the first dot is considered the divider for the composite database.
 
 Consider the query with parameter:
 
@@ -466,13 +468,15 @@ Consider the query with parameter:
 .Query
 [source, cypher]
 ----
-CYPHER 5 CREATE ALIAS $aliasname FOR DATABASE `northwind-graph`
+CYPHER 5 CREATE ALIAS $aliasname FOR DATABASE `northwind-graph`;
 ----
 
-If the composite database `mysimplecompositedatabase` exists, then a database alias `myalias` will be created in that composite database.
-If no such composite database exists, then a database alias `mysimplecompositedatabase.myalias` will be created.
+If the composite database `mySimpleCompositeDatabase` exists, then a database alias `myAlias` will be created in that composite database.
+If no such composite database exists, then a database alias `mySimpleCompositeDatabase.myAlias` will be created.
 
-On the contrary, a database alias `myalias` cannot be created in composite `mycompositedatabase.withdot` using parameters.
+===== Parameters with multiple dots
+
+On the contrary, a database alias `myAlias` cannot be created in composite `myCompositeDatabase.withDot` using parameters.
 Consider the same query but with the following parameter:
 
 .Parameters
@@ -488,22 +492,20 @@ If `mycompositedatabase` does not exist, the command will create a database alia
 
 In these cases, it is recommended to avoid parameters and explicitly quote the composite database name and alias name separately to avoid ambiguity.
 
-==== Handling parameters
+==== Avoiding ambiguity when using parameters
 
-Further special handling with parameters is needed for database aliases and similarly named composite databases.
+Database aliases and similarly named composite databases require further special handling with parameters.
 
 Consider the setup:
 
 .Query
 [source, cypher, role="noheader test-skip"]
 ----
-CYPHER 5 CREATE COMPOSITE DATABASE foo
-CYPHER 5 CREATE ALIAS `foo.bar` FOR DATABASE `northwind-graph`
+CYPHER 5 CREATE COMPOSITE DATABASE foo;
+CYPHER 5 CREATE ALIAS `foo.bar` FOR DATABASE `northwind-graph`;
 ----
 
-The alias `foo.bar` does not belong to the composite database `foo`.
-
-Dropping this alias using parameters fails with an error about a missing alias:
+Because the alias `foo.bar` does not belong to the composite database `foo`, dropping this alias using a parameter will fail with a chain of errors about a missing alias:
 
 .Parameters
 [source, javascript]
@@ -516,17 +518,18 @@ Dropping this alias using parameters fails with an error about a missing alias:
 .Query
 [source, cypher, role=test-fail]
 ----
-CYPHER 5 DROP ALIAS $aliasname FOR DATABASE
+CYPHER 5 DROP ALIAS $aliasname FOR DATABASE;
 ----
 
-.Error message
+.Error
 [source, output, role="noheader"]
 ----
-Failed to delete the specified database alias 'foo.bar': Database alias does not exist.
+42N00: Syntax error or access rule violation - graph reference not found. A graph reference with the name `foo.bar` was not found. Verify that the spelling is correct.
+42N51: Syntax error or access rule violation - invalid parameter. Invalid parameter $`aliasname`.
+42001: Syntax error or access rule violation - invalid syntax
 ----
 
-//From 5.26 onwards, the error message also contains the GQLSTATUS code `50N00` and the status description `error: general processing exception - internal error. Internal exception raised { $msgTitle }: Failed to create the specified database alias 'foo.bar'. Database alias does not exist.`
-
-Had the composite database `foo` not existed, the database alias `foo.bar` would have been dropped.
-
+In this example, Neo4j looks for the alias `bar` within the composite database `foo`.
+Since no such alias exists, the operation cannot be completed.
+If the composite database `foo` did not exist, the alias `foo.bar` would be resolved as a standalone alias and could be dropped successfully.
 In these cases, it is recommended to avoid parameters and explicitly quote the composite database name and alias name separately to avoid ambiguity.