Merge branch 'dev' into dev_add_coll_functions

Author: rsill-neo4j

antora.yml

@@ -7,4 +7,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.10'
+    neo4j-version: '2025.11'

modules/ROOT/pages/appendix/gql-conformance/analogous-cypher.adoc

@@ -31,11 +31,6 @@ These codes order the features in the table below.
 | * GQL's `PERCENTILE_CONT()` function is equivalent to Cypher's xref:functions/aggregating.adoc#functions-percentilecont[`percentileCont()`] function.
 * GQL's `PERCENTILE_DISC()` function is equivalent to Cypher's xref:functions/aggregating.adoc#functions-percentiledisc[`percentileDisc()`] function.
 
-| GQ09
-| `LET` statement
-| Adds columns to the current working table.
-Cypher uses xref:clauses/with.adoc[`WITH`] instead.
-
 | GQ10, GQ11, GQ23, GQ24
 | `FOR` statement: list value support, binding table support, `WITH ORDINALITY`, `WITH OFFSET`
 | Unnests a list or a binding table by expanding the current working table.

modules/ROOT/pages/clauses/use.adoc

@@ -36,7 +36,7 @@ Targeting multiple databases is not allowed, unless connected to a composite dat
 When connected to a non-composite database, the `USE` clause can only appear as the prefix of schema commands, or as the first clause of queries. There may be multiple `USE` clauses as long as they target the same database.
 
 == USE clause when connected to a composite database
-When executing queries against a link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[composite database], the `USE` clause must only refer to graphs that are part of the current composite database. The constituents can be listed either with `RETURN graph.names()` when connected to the composite database or `SHOW DATABASES YIELD name, constituents RETURN *`.
+When executing queries against a link:{neo4j-docs-base-uri}/operations-manual/current/scalability/composite-databases/concepts/[composite database], the `USE` clause must only refer to graphs that are part of the current composite database. The constituents can be listed either with `RETURN graph.names()` when connected to the composite database or `SHOW DATABASES YIELD name, constituents RETURN *`.
 
 === Position of use clauses
 When running queries against a composite database, the `USE` clause can appear as the first clause of:

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

@@ -627,7 +627,7 @@ If not specified, the default language for the database is set to the default la
 For more information, see the following sections in the Operations Manual:
 
 * link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/standard-databases/create-databases/#_set_a_default_cypher_version_for_a_standard_database[Set a default Cypher version for a standard database].
-* link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/create-composite-databases/#composite-databases-default-language[Set the default Cypher version for a composite database].
+* link:{neo4j-docs-base-uri}/operations-manual/current/scalability/composite-databases/create-composite-databases/#composite-databases-default-language[Set the default Cypher version for a composite database].
 
 a|
 label:functionality[]
@@ -1392,7 +1392,7 @@ DROP [COMPOSITE] DATABASE ... [RESTRICT \| CASCADE ALIAS[ES]]
 
 | Added the ability to drop database aliases while deleting a database.
 This will affect local database aliases targeting the database and constituent database aliases belonging to the composite database.
-For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/standard-databases/delete-databases/#delete-databases-with-aliases[Delete a database with local database aliases targeting it] and link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/delete-composite-databases/#composite-databases-delete-with-aliases[Delete a composite database with constituent database aliases].
+For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/standard-databases/delete-databases/#delete-databases-with-aliases[Delete a database with local database aliases targeting it] and link:{neo4j-docs-base-uri}/operations-manual/current/scalability/composite-databases/delete-composite-databases/#composite-databases-delete-with-aliases[Delete a composite database with constituent database aliases].
 
 a|
 label:functionality[]

modules/ROOT/pages/expressions/list-expressions.adoc

@@ -301,7 +301,7 @@ RETURN list[0] + [2] + list[1..] AS newList
 [[list-concatenation]]
 == List concatenation
 
-Cypher contains two list concatenation operators: `||` and `+`.
+Cypher contains two list concatenation operators: `||` and `\+`.
 `||` is xref:appendix/gql-conformance/index.adoc[GQL conformant], while `+` is not.
 
 .List concatenation using `||` and `+`

modules/ROOT/pages/functions/graph.adoc

@@ -16,7 +16,7 @@
 
 .Considerations
 |===
-| `graph.names()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[composite databases].
+| `graph.names()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/scalability/composite-databases/concepts/[composite databases].
 |===
 
 .+graph.names()+
@@ -71,7 +71,7 @@ The names of all graphs on the current composite database are returned.
 
 .Considerations
 |===
-| `graph.propertiesByName()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[composite databases].
+| `graph.propertiesByName()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/scalability/composite-databases/concepts/[composite databases].
 | The properties in the returned `MAP` are set on the link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/aliases/manage-aliases-standard-databases/[alias]that adds the graph as a constituent of a composite database.
 |===
 

modules/ROOT/pages/functions/scalar.adoc

@@ -383,8 +383,8 @@ It is therefore recommended to use application-generated IDs instead.
 
 [NOTE]
 ====
-On a link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[composite database], the `id()` function should be used with caution.
-It is recommended to use xref:functions/scalar.adoc#functions-elementid[`elementId()`] instead. 
+On a link:{neo4j-docs-base-uri}/operations-manual/current/scalability/composite-databases/concepts/[composite database], the `id()` function should be used with caution.
+It is recommended to use xref:functions/scalar.adoc#functions-elementid[`elementId()`] instead.
 
 When called in database-specific subqueries, the resulting ID value for a node or relationship is local to that database.
 The local ID for nodes or relationships from different databases may be the same.

modules/ROOT/pages/introduction/cypher-neo4j.adoc

@@ -74,7 +74,7 @@ Normally there is only one graph within each database, and many administrative c
 Cypher queries executed in a session may declare which graph they apply to, or use a default, given by the session.
 Composite databases can contain multiple graphs, by means of aliases to other databases.
 Queries submitted to composite databases may refer to multiple graphs within the same query.
-For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[Operations manual -> Composite databases].
+For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/scalability/composite-databases/concepts/[Operations manual -> Composite databases].
 
 *Database*:: A database is a storage and retrieval mechanism for collecting data in a defined space on disk and in memory.