Merge branch 'cypher-25' into cypher_25_yml_readme_updates

Author: JPryce-Aklundh

modules/ROOT/content-nav.adoc

@@ -94,8 +94,8 @@
 ** xref:indexes/syntax.adoc[]
 
 * xref:constraints/index.adoc[]
+** xref:constraints/managing-constraints.adoc[]
 ** xref:constraints/syntax.adoc[]
-** xref:constraints/examples.adoc[]
 
 * xref:planning-and-tuning/index.adoc[]
 ** xref:planning-and-tuning/execution-plans.adoc[]

modules/ROOT/images/graph_match_clause.svg

@@ -301,7 +301,9 @@ Either the pattern already exists, or it needs to be created.
 | Returns a 2D or 3D point object, given two or respectively three coordinate values in the Cartesian coordinate system or WGS 84 geographic coordinate system.
 
 | xref:functions/spatial.adoc#functions-point-distance[`point.distance()`]
-| Returns a `FLOAT` representing the geodesic distance between any two points in the same CRS.
+| Returns a `FLOAT` representing the distance between any two points in the same CRS.
+If the points are in the WGS 84 CRS, the function returns the geodesic distance (i.e., the shortest path along the curved surface of the Earth).
+If the points are in a Cartesian CRS, the function returns the Euclidean distance (i.e., the shortest straight-line distance in a flat, planar space).
 
 | xref:functions/spatial.adoc#functions-point-withinBBox[`point.withinBBox()`]
 | Returns true if the provided point is within the bounding box defined by the two provided points.
@@ -507,29 +509,17 @@ GQL supports `GRAPH TYPES` as a way of constraining a graph schema, but does not
 | Cypher feature
 | Description
 
-| xref:constraints/examples.adoc#constraints-examples-node-uniqueness[Node property uniqueness constraints]
-| Ensures that certain nodes have a set of specified properties whose combined value is unique when all properties exist on the node
+| xref:constraints/managing-constraints.adoc#create-property-uniqueness-constraints[Property uniqueness constraints]
+| Ensures that the combined property values are unique for all nodes with a specific label or all relationships with a specific type.
 
-| xref:constraints/examples.adoc#constraints-examples-relationship-uniqueness[Relationship property uniqueness constraints]
-| Ensures that certain relationships have a set of specified properties whose combined value is unique when all properties exist on the relationship.
+| xref:constraints/managing-constraints.adoc#create-property-existence-constraints[Property existence constraints]
+| Ensures that a property exists either for all nodes with a specific label or for all relationships with a specific type.
 
-| xref:constraints/examples.adoc#constraints-examples-node-property-existence[Node property existence constraints]
-| Ensures that certain nodes have a specified property.
+| xref:constraints/managing-constraints.adoc#create-property-type-constraints[Property type constraints]
+| Ensures that a property has the required property type for all nodes with a specific label or for all relationships with a specific type.
 
-| xref:constraints/examples.adoc#constraints-examples-relationship-property-existence[Relationship property existence constraints]
-| Ensures that certain relationships have a specified property.
-
-| xref:constraints/examples.adoc#constraints-examples-node-property-type[Node property type constraints]
-| Ensures that certain nodes have a property of the required property type when the property exists on the node.
-
-| xref:constraints/examples.adoc#constraints-examples-relationship-property-type[Relationship property type constraints]
-| Ensures that certain relationships have a property of the required property type when the property exists on the relationship.
-
-| xref:constraints/examples.adoc#constraints-examples-node-key[Node key constraints]
-| Ensures that certain nodes have a set of specified properties whose combined value is unique and all properties in the set are present.
-
-| xref:constraints/examples.adoc#constraints-examples-relationship-key[Relationship key constraints]
-| Ensures that certain relationships have a set of defined properties whose combined value is unique. It also ensures that all properties in the set are present.
+| xref:constraints/managing-constraints.adoc#create-key-constraints[Key constraints]
+| Ensures that all properties exist and that the combined property values are unique for all nodes with a specific label or all relationships with a specific type.
 
 |===
 

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

@@ -1,8 +1,8 @@
 :description: Overview of Cypher's conformance to GQL.
 = GQL conformance
 
-*Last updated*: 13 September 2024 +
-*Neo4j version*: 5.24
+*Last updated*: 24 October 2024 +
+*Neo4j version*: 5.25
 
 GQL is the new link:https://www.iso.org/home.html[ISO] International Standard query language for graph databases.
 

modules/ROOT/pages/appendix/gql-conformance/index.adoc

@@ -93,6 +93,11 @@ These codes order the features in the table below.
 | xref:patterns/reference.adoc#graph-patterns-rules-variable-references[Graph patterns -> Rules]
 |
 
+| GB01
+| Long identifiers
+| xref:syntax/naming.adoc#identifier-length-limit[Naming rules and recommendations -> Identifier length limit]
+|
+
 | 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/appendix/gql-conformance/supported-optional.adoc

@@ -15,7 +15,7 @@ Let's explain how to use these features with a more advanced query tuning exampl
 
 [NOTE]
 ====
-If you are upgrading an existing store to {neo4j-version-exact}, it may be necessary to drop and re-create existing indexes.
+If you are upgrading an existing store, it may be necessary to drop and re-create existing indexes.
 For information on native index support and upgrade considerations regarding indexes, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/performance/index-configuration[Operations Manual -> Performance -> Index configuration].
 ====
 
@@ -936,10 +936,10 @@ Predicates that will not work:
 
 [NOTE]
 ====
-If there is an existence constraint on the property, no predicate is required to trigger the optimization.
+If there is a xref:constraints/managing-constraints.adoc#create-property-existence-constraints[property existence constraint] on the property, no predicate is required to trigger the optimization.
 For example, `CREATE CONSTRAINT constraint_name FOR (p:Person) REQUIRE p.name IS NOT NULL`
 
-As of Neo4j {neo4j-version-exact}, predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
+Predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
 The only exception are queries with parameters of type `POINT`.
 ====
 

modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc

@@ -259,7 +259,7 @@ A `VOID` procedure is a procedure that does not declare any result fields and re
 `VOID` procedure only produces side-effects and does not allow for the use of `YIELD`.
 Calling a `VOID` procedure in the middle of a larger query will simply pass on each input record (i.e., it acts like xref:clauses/with.adoc[`WITH *`] in terms of the record stream).
 
-[role=label--new-5.24]
+
 [[optional-call]]
 == Optional procedure calls
 

modules/ROOT/pages/clauses/call.adoc

@@ -573,8 +573,7 @@ Later invocations of the subquery can observe writes made by earlier invocations
 Using the same example graph as above, this example shows the table of intermediate results and the state of the graph after each clause for the following query:
 
 [NOTE]
-The below query uses a xref:subqueries/call-subquery.adoc#variable-scope-clause[variable scope clause] (introduced in Neo4j 5.23) to import variables into the `CALL` subquery.
-If you are using an older version of Neo4j, use an xref:subqueries/call-subquery.adoc#importing-with[importing `WITH` clause] instead.
+The below query uses a xref:subqueries/call-subquery.adoc#variable-scope-clause[variable scope clause] to import variables into the `CALL` subquery.
 
 [source,cypher]
 ----

modules/ROOT/pages/clauses/clause-composition.adoc

@@ -23,7 +23,7 @@ Multiple labels are separated by colons.
 CREATE (charlie:Person:Actor {name: 'Charlie Sheen'}), (oliver:Person:Director {name: 'Oliver Stone'})
 ----
 
-As of Neo4j 5.18, multiple labels can also be separated by an ampersand `&`, in the same manner as it is used in xref:patterns/reference.adoc#label-expressions[label expressions].
+Multiple labels can also be separated by an ampersand `&`, in the same manner as it is used in xref:patterns/reference.adoc#label-expressions[label expressions].
 Separation by colon `:` and ampersand `&` cannot be mixed in the same clause.
 
 .Query
@@ -205,7 +205,7 @@ Nodes created: 2 +
 Properties set: 4
 |===
 
-[role=label--new-5.18]
+
 [[insert-as-synonym-of-create]]
 == `INSERT` as a synonym of `CREATE`
 

modules/ROOT/pages/clauses/create.adoc

@@ -58,7 +58,7 @@ This query is only possible to run on nodes without any relationships connected
 Deleted 1 node
 ----
 
-[role=label--new-5.14]
+
 [[delete-nodetach]]
 === NODETACH keyword