Merge branch 'cypher-25' into conditional_clause

Author: JPryce-Aklundh

antora.yml

@@ -6,4 +6,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.02'
+    neo4j-version: '2025.03'

modules/ROOT/pages/appendix/gql-conformance/supported-optional.adoc

@@ -98,6 +98,18 @@ These codes order the features in the table below.
 | xref:syntax/naming.adoc#identifier-length-limit[Naming rules and recommendations -> Identifier length limit]
 |
 
+| GD01
+| Updatable graphs
+| xref:clauses/clause-composition.adoc#writing-clauses[Cypher clauses -> Writing clauses]
+| * Feature GD01 implies compliance with GQL feature GT01, "Explicit transaction commands", which states that conforming languages shall contain the following transaction control commands: `START TRANSACTION`, `ROLLBACK`, and `COMMIT`.
+These are not present in Cypher.
+However, Neo4j offers transaction management through the link:{neo4j-docs-base-uri}/create-applications[driver] transaction API.
+Cypher Shell also offers specific link:{neo4j-docs-base-uri}/operations-manual/current/tools/cypher-shell/#cypher-shell-commands[commands] to manage transactions.
+* Feature GD01 implies conformance to GQL's `<set-statement>` (subclause 13.3).
+GQL’s `SET` has no order dependencies because all right-hand side operations are completed before any assignments occur.
+However, In Cypher’s `SET`, the order of rows can affect the outcome because changes made during execution may depend on the sequence of assignments.
+The only way to guarantee row order in Neo4j is to use xref:clauses/order-by.adoc[`ORDER BY`]. 
+
 | GF01
 | Enhanced numeric functions
 | xref:functions/mathematical-numeric.adoc#functions-abs[`abs()`], xref:functions/mathematical-numeric.adoc#functions-floor[`floor()`], xref:functions/mathematical-logarithmic.adoc#functions-sqrt[`sqrt()`].

modules/ROOT/pages/clauses/call.adoc

@@ -86,7 +86,7 @@ CALL dbms.checkConfigValue('server.bolt.enabled', 'true')
 | "valid" | "message"
 | true | "requires restart"
 
-2+d|Rows: 2
+2+d|Rows: 1
 |===
 
 ====
@@ -118,7 +118,7 @@ CALL dbms.checkConfigValue($setting, $value)
 | "valid" | "message"
 | true | "requires restart"
 
-2+d|Rows: 2
+2+d|Rows: 1
 |===
 
 [NOTE]
@@ -153,7 +153,7 @@ CALL dbms.checkConfigValue($setting, 'true')
 | "valid" | "message"
 | true | "requires restart"
 
-2+d|Rows: 2
+2+d|Rows: 1
 |===
 
 ====

modules/ROOT/pages/clauses/where.adoc

@@ -368,7 +368,8 @@ For more information, see the section about the xref:syntax/operators.adoc#match
 | 'Andy'
 | 'Timothy'
 | 'Peter'
-1+|Rows: 3
+
+1+d|Rows: 3
 |===
 
 Note that the `IS NORMALIZED` operator returns `null` when used on a non-`STRING` value.

modules/ROOT/pages/clauses/with.adoc

@@ -25,10 +25,6 @@ Another use is to filter on aggregated values.
 `WITH` is used to introduce aggregates which can then be used in predicates in `WHERE`.
 These aggregate expressions create new bindings in the results.
 
-`WITH` is also used to separate reading from updating of the graph.
-Every part of a query must be either read-only or write-only.
-When going from a writing part to a reading part, the switch must be done with a `WITH` clause.
-
 image:graph_with_clause.svg[]
 
 ////

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

@@ -16,8 +16,8 @@ New features are added to the language continuously, and occasionally, some feat
 This section lists all of the features that have been removed, deprecated, added, or extended in different Cypher versions.
 Replacement syntax for deprecated and removed features are also indicated.
 
-[[cypher-deprecations-additions-removals-2025.02]]
-== Neo4j 2025.02
+[[cypher-deprecations-additions-removals-2025.03]]
+== Neo4j 2025.03
 
 === Removed features
 [cols="2", options="header"]
@@ -173,6 +173,18 @@ Graph name parts with special characters may require additional escaping of thos
 
 Note that escaping graph names within the graph functions string argument is not supported in Cypher 5.
 
+a|
+label:functionality[]
+label:updated[]
+[source, cypher, role="noheader"]
+----
+CREATE (:Person)
+MATCH (p:Person)
+RETURN count(p) AS count
+----
+
+| Queries no longer require xref:clauses/with.adoc[`WITH`] to transition between reading and writing operations.
+
 |===
 
 === New features

modules/ROOT/pages/functions/aggregating.adoc

@@ -312,8 +312,8 @@ The `Guy Pearce` node will, therefore, get counted twice when not using `DISTINC
 
 | friendOfFriend.name  | count(friendOfFriend) | count(ALL friendOfFriend)    | count(DISTINCT friendOfFriend)
 | "Guy Pearce" | 2 | 2 | 1
-4+d|Rows: 1
 
+4+d|Rows: 1
 |===
 
 ======

modules/ROOT/pages/functions/temporal/duration.adoc

@@ -19,7 +19,7 @@ See also xref::values-and-types/temporal.adoc[Temporal values] and xref::syntax/
 | *Syntax* 3+| `duration(input)`
 | *Description* 3+| Creates a `DURATION` value.
 .2+| *Arguments* | *Name* | *Type* | *Description*
-| `input` | `ANY` | A map optionally containing the following keys: 'years', 'quarters', 'months', 'weeks', 'days', 'hours', 'minutes', 'seconds', 'milliseconds', 'microseconds', or 'nanoseconds'.
+| `input` | `ANY` | A map optionally containing the following keys: 'years', 'months', 'weeks', 'days', 'hours', 'minutes', 'seconds', 'milliseconds', 'microseconds', or 'nanoseconds'.
 | *Returns* 3+| `DURATION`
 |===
 

modules/ROOT/pages/genai-integrations.adoc

@@ -177,27 +177,29 @@ CALL db.create.setNodeVectorProperty(moviesList[index], 'embedding', vector) //
 [source, cypher, role=test-skip]
 ----
 MATCH (m:Movie WHERE m.plot IS NOT NULL)
-WITH collect(m) AS moviesList // <1>
+WITH collect(m) AS moviesList, // <1>
      count(*) AS total,
      100 AS batchSize // <2>
-UNWIND range(0, total, batchSize) AS batchStart // <3>
+UNWIND range(0, total-1, batchSize) AS batchStart // <3>
 CALL (moviesList, batchStart, batchSize) { // <4>
     WITH [movie IN moviesList[batchStart .. batchStart + batchSize] | movie.title || ': ' || movie.plot] AS batch // <5>
     CALL genai.vector.encodeBatch(batch, 'OpenAI', { token: $token }) YIELD index, vector
     CALL db.create.setNodeVectorProperty(moviesList[batchStart + index], 'embedding', vector) // <6>
-} IN TRANSACTIONS OF 1 ROW <7>
+} IN CONCURRENT TRANSACTIONS OF 1 ROW <7>
 ----
 
 <1> xref:functions/aggregating.adoc#functions-collect[Collect] all returned `Movie` nodes into a `LIST<NODE>`.
 <2> `batchSize` defines the number of nodes in `moviesList` to be processed at once.
 Because vector embeddings can be very large, a larger batch size may require significantly more memory on the Neo4j server.
 Too large a batch size may also exceed the provider's threshold.
 <3> Process `Movie` nodes in increments of `batchSize`.
+The end range `total-1` is due to `range` being inclusive on both ends.
 <4> A xref:subqueries/subqueries-in-transactions.adoc[`CALL` subquery] executes a separate transaction for each batch.
 Note that this `CALL` subquery uses a xref:subqueries/call-subquery.adoc#variable-scope-clause[variable scope clause].
 <5> `batch` is a list of strings, each being the concatenation of `title` and `plot` of one movie.
 <6> The procedure sets `vector` as value for the property named `embedding` for the node at position `batchStart + index` in the `moviesList`.
 <7> Set to `1` the amount of batches to be processed at once.
+For more information on concurrency in transactions, see xref:subqueries/subqueries-in-transactions.adoc#concurrent-transactions[`CALL` subqueries -> Concurrent transactions]).
 
 [NOTE]
 This example may not scale to larger datasets, as `collect(m)` requires the whole result set to be loaded in memory.

modules/ROOT/pages/patterns/shortest-paths.adoc

@@ -64,7 +64,7 @@ CREATE (asc)-[:LINK {distance: 7.25}]->(cnm),
   (wof)-[:LINK {distance: 0.65}]->(wos)
 ----
 
-The paths matched by a xref:patterns/fixed-length-patterns.adoc#path-patterns[path pattern] can be restricted to only the shortest (by number of hops) by including the keyword `SHORTEST k`, where `k` is the number of paths to match, and can be either an `INTEGER` literal or, as of Neo4j 2025.02, a parameter which resolves to an `INTEGER`.
+The paths matched by a xref:patterns/fixed-length-patterns.adoc#path-patterns[path pattern] can be restricted to only the shortest (by number of hops) by including the keyword `SHORTEST k`, where `k` is the number of paths to match, and can be either an `INTEGER` literal or, as of Neo4j 2025.03, a parameter which resolves to an `INTEGER`.
 For example, the following example uses `SHORTEST 1` to return the length of the shortest path between `Worcester Shrub Hill` and `Bromsgrove`:
 
 .Query