Merge branch 'dev' into pascal-case-wording

rsill-neo4j · web-flow · commit a55c089709b2 · 2025-11-07T09:28:05.000+01:00
diff --git a/antora.yml b/antora.yml
@@ -7,4 +7,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.10'
+    neo4j-version: '2025.11'
diff --git a/modules/ROOT/pages/appendix/gql-conformance/analogous-cypher.adoc b/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.
diff --git a/modules/ROOT/pages/clauses/use.adoc b/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:
diff --git a/modules/ROOT/pages/constraints/managing-constraints.adoc b/modules/ROOT/pages/constraints/managing-constraints.adoc
@@ -344,6 +344,7 @@ Added 1 constraint.
 
 ======
 
+[[vector-type-constraints]]
 .Create `VECTOR` property type constraints label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.10]
 ======
 
@@ -452,6 +453,8 @@ The allowed property types for property type constraints are:
 
 [NOTE]
 Because storing lists of xref:values-and-types/vector.adoc[`VECTOR`] values is not supported, property type constraints cannot be created for `LIST<VECTOR<TYPE>(DIMENSION) NOT NULL>`.
+Additionally, `VECTOR` property type constraints must be created with a specific dimension and coordinate value, where the dimension must be greater than `0` and less than or equal to `4096`.
+For more information, see xref:values-and-types/vector.adoc[Values and types -> Vectors].
 
 For a complete reference describing all types available in Cypher, see the section on xref::values-and-types/property-structural-constructed.adoc#types-synonyms[types and their synonyms].
 
diff --git a/modules/ROOT/pages/constraints/syntax.adoc b/modules/ROOT/pages/constraints/syntax.adoc
@@ -138,7 +138,7 @@ Where `<TYPE>` is one of the following property types:
 
 [NOTE]
 Because storing lists of xref:values-and-types/vector.adoc[`VECTOR`] values is not supported, property type constraints cannot be created for `LIST<VECTOR<TYPE>(DIMENSION) NOT NULL>`.
-Additionally, `VECTOR` property type constraints must be created with a specific dimension and coordinate value, where the dimension must be greater than `0` and less or equal to `4096`.
+Additionally, `VECTOR` property type constraints must be created with a specific dimension and coordinate value, where the dimension must be greater than `0` and less than or equal to `4096`.
 For more information, see xref:values-and-types/vector.adoc[Values and types -> Vectors].
 
 Allowed syntax variations of these types are listed in  xref::values-and-types/property-structural-constructed.adoc#types-synonyms[Types and their synonyms].
diff --git a/modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc b/modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
@@ -598,7 +598,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[]
@@ -1363,7 +1363,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[]
diff --git a/modules/ROOT/pages/expressions/list-expressions.adoc b/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 `+`
diff --git a/modules/ROOT/pages/functions/graph.adoc b/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.
 |===
 
diff --git a/modules/ROOT/pages/functions/predicate.adoc b/modules/ROOT/pages/functions/predicate.adoc
@@ -110,7 +110,9 @@ RETURN all(i in emptyList WHERE true) as allTrue, all(i in emptyList WHERE false
 |===
 | *Syntax* 3+| `allReduce(accumulator = initial, stepVariable IN list \| reductionFunction, predicate)`
 | *Description* 3+| Returns true if, during the stepwise evaluation of a value across the elements in a given `LIST<ANY>`, the accumulated result satisfies a specified predicate at every step.
-Where that list is a xref:patterns/variable-length-patterns.adoc#group-variables[group variable] defined in a xref:patterns/variable-length-patterns.adoc#quantified-path-patterns[quantified path pattern], it allows for the early pruning of paths that do not satisfy the predicate.
+If that list is a xref:patterns/variable-length-patterns.adoc#group-variables[group variable] defined in a xref:patterns/variable-length-patterns.adoc#quantified-path-patterns[quantified path pattern], its predicate is inlined where applicable.
+This inlining allows for early pruning of the search space by discarding paths as soon as the predicate is not satisfied.
+Note that `allReduce()` predicates are not inlined when used in a xref:patterns/shortest-paths.adoc[shortest path pattern], and therefore do not benefit from this pruning.
 .7+| *Arguments* | *Name* | *Type* | *Description*
 | `accumulator` | `ANY` | A variable that holds the result of the `reductionFunction` as the `list` is iterated.
 It is initialized with the value of `initial`.
diff --git a/modules/ROOT/pages/functions/scalar.adoc b/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.
diff --git a/modules/ROOT/pages/indexes/search-performance-indexes/managing-indexes.adoc b/modules/ROOT/pages/indexes/search-performance-indexes/managing-indexes.adoc
@@ -954,11 +954,11 @@ The below table contains the full information about all columns returned by the
 | `FLOAT`
 
 | `type`
-| The IndexType of this index (`FULLTEXT`, `LOOKUP`, `POINT`, `RANGE`, or `TEXT`). label:default-output[]
+| The IndexType of this index (`FULLTEXT`, `LOOKUP`, `POINT`, `RANGE`, `TEXT`, or `VECTOR`). label:default-output[]
 | `STRING`
 
 | `entityType`
-| Type of entities this index represents (nodes or relationship). label:default-output[]
+| Type of entities this index represents (`NODE` or `RELATIONSHIP`). label:default-output[]
 | `STRING`
 
 | `labelsOrTypes`
diff --git a/modules/ROOT/pages/introduction/cypher-neo4j.adoc b/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.
 
diff --git a/modules/ROOT/pages/patterns/variable-length-patterns.adoc b/modules/ROOT/pages/patterns/variable-length-patterns.adoc
@@ -380,6 +380,10 @@ For example, all relationships in the path must be of type `EMPLOYED_BY`.
 * Nodes or relationships must have properties satisfying some condition.
 For example, all relationships must have the property `distance > 10`.
 
+* For every iteration of the quantified path pattern, an aggregated value over the constructed path so far must satisfy a predicate.
+For example, the sum of the property `distance` of the relationships in the path must be less than 50 for every step in the construction of the path.
+See xref::functions/predicate.adoc#functions-allreduce[allReduce] for more information about this predicate.
+
 To demonstrate the utility of predicates in quantified path patterns, this section considers an example of finding the shortest path by physical distance and compares that to the results yielded by using the xref:patterns/shortest-paths.adoc[`SHORTEST`] keyword.
 The graph in this example continues with `Station` nodes, but adds both a geospatial `location` property to the `Stations`, as well as `LINK` relationships with a `distance` property representing the distance between pairs of `Stations`:
 
@@ -558,6 +562,26 @@ This query avoids having to find all possible paths and then imposing a `LIMIT 1
 It also shows that there is only one path to solving the query (a number that remains constant even if the data from the rest of the UK railway network was included).
 Using inline predicates or making quantified path patterns more specific where possible can thus greatly improve query performance.
 
+An alternative is to use an upper bound for the total distance, for example `6.05`.
+Once a path exceeds this upper bound, you can prune it and continue searching other paths.
+The xref::functions/predicate.adoc#functions-allreduce[allReduce] predicate function expresses this as follows:
+
+.Query
+[source,cypher]
+----
+MATCH (bfr:Station {name: "London Blackfriars"}),
+      (ndl:Station {name: "North Dulwich"})
+MATCH p = (bfr) ((a)-[l:LINK]-(b:Station))+ (ndl)
+WHERE allReduce(
+  pathLength = 0,
+  link IN l | pathLength + link.distance,
+  pathLength < 6.05
+)
+RETURN reduce(acc = 0, r in relationships(p) | round(acc + r.distance, 2))
+  AS distance
+ORDER BY distance LIMIT 1
+----
+
 [[further-reading]]
 == Further reading
 
diff --git a/modules/ROOT/pages/planning-and-tuning/operators/operators-detail.adoc b/modules/ROOT/pages/planning-and-tuning/operators/operators-detail.adoc
diff --git a/modules/ROOT/pages/queries/select-version.adoc b/modules/ROOT/pages/queries/select-version.adoc
diff --git a/modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc b/modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc
diff --git a/modules/ROOT/pages/values-and-types/graph-references.adoc b/modules/ROOT/pages/values-and-types/graph-references.adoc
diff --git a/modules/ROOT/pages/values-and-types/vector.adoc b/modules/ROOT/pages/values-and-types/vector.adoc
