syntax, fixes, and additions

Author: JPryce-Aklundh

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

@@ -22,6 +22,127 @@ Cypher 25 was introduced in Neo4j 2025.06 and can only be used on Neo4j 2025.06+
 Features removed in Cypher 25 are still available on Neo4j 2025.06+ databases either by prepending a query with `CYPHER 5` or by having Cypher 5 as the default language for the database.
 For more information, see xref:queries/select-version.adoc[].
 
+[[cypher-deprecations-additions-removals-2025.xx]]
+== Neo4j 2025.xx
+
+=== Updated in Cypher 25
+
+[cols="2", options="header"]
+|===
+| Feature
+| Details
+
+a|
+label:functionality[]
+label:updated[]
+[source, cypher, role="noheader"]
+----
+SHOW CONSTRAINTS YIELD name, enforcedLabel, classification
+----
+
+a| 
+Introduced two new columns returned by `SHOW CONSTRAINTS`:
+
+* `enforcedLabel`: shows the implied labels belonging to a node element type, and the source and target node labels belonging to a relationship element type.
+* `classification`: shows the status of a constraint in a graph type.
+
+For more information, see xref:schema/constraints/list-constraints.adoc#list-constraints-result-columns[Constraints -> Result columns for listing constraints] and xref:schema/graph-types/list-graph-types.adoc#graph-type-elements-in-show-constraints[Graph types -> Graph type elements in `SHOW CONSTRAINTS`].
+
+a|
+label:functionality[]
+label:updated[]
+[source, syntax, role="noheader"]
+----
+SHOW NODE EXIST[ENCE] \| EXIST[ENCE] CONSTRAINTS
+----
+
+| The `NODE EXIST[ENCE]` and `EXIST[ENCE]` type filtering options allowed by the `SHOW CONSTRAINTS` command now also return node label existence constraints (crated as part of node element types in a xref:schema/graph-types/index.adoc[graph type]).
+For more information, see xref:schema/syntax.adoc#constraints-syntax-list-type-filter[Syntax -> Type filters].
+
+|===
+
+=== New in Cypher 25
+
+[cols="2", options="header"]
+|===
+| Feature
+| Details
+
+a|
+label:functionality[]
+label:new[]
+[source, cypher, role="noheader"]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (:Person => :Resident {name :: STRING NOT NULL}),
+    (:Pet => :Resident&Animal {healthCertificate :: STRING, name :: STRING}),
+    (:City => {name :: STRING NOT NULL, population :: INTEGER}),
+    (:Resident)-[:LIVES_IN => {since :: DATE NOT NULL}]->(:City)
+}
+----
+
+| Introduced the ability to set a xref:schema/graph-types/index.adoc[graph type] for a database using the `ALTER CURRENT GRAPH TYPE SET` command.
+A graph type enforces holistically an open schema, providing a defined structure for an entire graph, and includes constraint types (node label existence, relationship source node, and relationship target node constraints) not possible to create using the older `CREATE CONSTRAINT` syntax.
+For more information, see xref:schema/graph-types/set-graph-types.adoc[].
+
+a|
+label:functionality[]
+label:new[]
+[source, cypher, role="noheader"]
+----
+ALTER CURRENT GRAPH TYPE ADD {
+  (p:Person => :Resident {name :: STRING, ssn :: INTEGER, nationality :: STRING})
+    REQUIRE (p.name, p.ssn) IS KEY,
+  CONSTRAINT pet_address FOR (pet:Pet) REQUIRE pet.address IS NOT NULL,
+  (:Animal => {type :: STRING NOT NULL})
+}
+----
+
+| Introduced the ability to extend graph types using the `ALTER CURRENT GRAPH TYPE ADD` command.
+For more information, see xref:schema/graph-types/extend-graph-types.adoc[].
+
+a|
+label:functionality[]
+label:new[]
+[source, cypher, role="noheader"]
+----
+ALTER CURRENT GRAPH TYPE ALTER {
+    (:Robot => :Resident&Machine {application :: STRING NOT NULL, id :: INTEGER NOT NULL}),
+    (:Resident)-[:LIVES_IN => {since :: ANY NOT NULL}]->(:City)
+}
+----
+
+| Introduced the ability to alter graph types using the `ALTER CURRENT GRAPH TYPE ALTER` command.
+For more information, see xref:schema/graph-types/alter-graph-types.adoc[].
+
+a|
+label:functionality[]
+label:new[]
+[source, cypher, role="noheader"]
+----
+SHOW CURRENT GRAPH TYPE
+----
+
+| Introduced the ability to show graph types using the `SHOW CURRENT GRAPH TYPE` command.
+For more information, see xref:schema/graph-types/list-graph-types.adoc[].
+
+a|
+label:functionality[]
+label:new[]
+[source, cypher, role="noheader"]
+----
+ALTER CURRENT GRAPH DROP {
+  (:Pet =>)
+}
+----
+
+| Introduced the ability to drop elements from graph types using the `ALTER CURRENT GRAPH TYPE DROP` command.
+For more information, see xref:schema/graph-types/drop-graph-type-elements.adoc[].
+|===
+
+
+
+
 [[cypher-deprecations-additions-removals-2025.09]]
 == Neo4j 2025.09
 

modules/ROOT/pages/schema/constraints/drop-constraints.adoc

@@ -53,6 +53,7 @@ CREATE CONSTRAINT node_uniqueness_param
 FOR (book:Book) REQUIRE book.prop1 IS UNIQUE;
 CREATE CONSTRAINT rel_exist_param
 FOR ()-[wrote:WROTE]-() REQUIRE wrote.published IS NOT NULL
+----
 ////
 
 .Drop a constraint by name

modules/ROOT/pages/schema/constraints/index.adoc

@@ -16,4 +16,14 @@ For information about listing and dropping constraints, see:
 * xref:schema/constraints/list-constraints.adoc[]
 * xref:schema/constraints/drop-constraints.adoc[]
 
-For reference material about the Cypher commands used to manage constraints, see xref:schema/syntax.adoc[].
+For reference material about the Cypher commands used to manage constraints, see xref:schema/syntax.adoc#constraints[Syntax -> Constraints].
+
+[NOTE]
+====
+All constraints created using the older xref:schema/constraints/create-constraints.adoc#create-constraint[`CREATE CONSTRAINT`] syntax will automatically be added to the graph type of a database.
+Not all constraint types can be created using this syntax, however, and maintaining individual constraints can become complicated over time as their number increases.
+
+*It is, therefore, recommended to define a schema using a graph type, which offers both additional, more sophisticated constraint types and a more holistic and simplified approach for constraining and maintaining the shape of the data in a graph.*
+
+For more information, see xref:schema/graph-types/index.adoc[]
+====

modules/ROOT/pages/schema/constraints/list-constraints.adoc

@@ -274,7 +274,7 @@ The list returned will only include a single value (the name of the constrained
 | LIST<STRING>
 
 | enforcedLabel
-| The implied labels required by a node element type. label:default-output[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
+| The implied labels required by a node element type or the source node and target node labels required by a relationship element type. label:default-output[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
 | STRING
 
 | ownedIndex

modules/ROOT/pages/schema/graph-types/alter-graph-types.adoc

@@ -24,11 +24,11 @@ ALTER CURRENT GRAPH TYPE SET {
     (:Pet => :Resident&Animal {insuranceNumber :: INTEGER IS KEY, healthCertificate :: STRING IS UNIQUE, name :: STRING}),
     (:Robot => :Resident {application :: STRING NOT NULL}),
     (:City => {name :: STRING NOT NULL, population :: INTEGER}),
-    (:Resident)-[:LIVES_IN => {since:: DATE NOT NULL}]->(:City),
+    (:Resident)-[:LIVES_IN => {since :: DATE NOT NULL}]->(:City),
     (:Company => {name :: STRING, address :: STRING IS UNIQUE}),
     (:Person)-[:WORKS_FOR => {role :: STRING}]->(:Company),
     CONSTRAINT company_name FOR (c:Company) REQUIRE c.name IS KEY,
-    CONSTRAINT animal_id FOR (a:Animal) REQUIRE a.Id IS UNIQUE,
+    CONSTRAINT animal_id FOR (a:Animal) REQUIRE a.id IS UNIQUE,
     CONSTRAINT resident_address FOR (resident:Resident) REQUIRE resident.address :: STRING
 }
 ----
@@ -41,16 +41,16 @@ For details about all the elements included in the above graph type, see xref:sc
 ----
 ALTER CURRENT GRAPH TYPE ALTER {
     (:Robot => :Resident&Machine {application :: STRING NOT NULL, id :: INTEGER NOT NULL}), // <1>
-    (:Resident)-[:LIVES_IN => {since:: ANY NOT NULL}]->(:City) // <2>
+    (:Resident)-[:LIVES_IN => {since :: ANY NOT NULL}]->(:City) // <2>
 }
 ----
 
 <1> Nodes with a `Robot` label must now also have a `Machine` label.
 `Robot` nodes are also required to have an `id` property of type `INTEGER`. 
 <2> `since` properties on `LIVES_IN` relationships can now be of `ANY` type (they were previously constrained to be of type `DATE`).
 
-.Updated graph type, showing altered node element type and relationship element type
-image::graph-types-alter-graph-type.svg[Graph type showing altered node element type and relationship element type, width=700, role=popup]
+.Updated data model, showing altered node element type and relationship element type in graph type
+image::graph-types-alter-graph-type.svg[Updated data model showing altered node element type and relationship element type in graph type, width=700, role=popup]
 
 This alteration is implemented by the _creation_ of the following constraints:
 

modules/ROOT/pages/schema/graph-types/drop-graph-type-elements.adoc

@@ -16,12 +16,12 @@ ALTER CURRENT GRAPH TYPE SET {
    (:Pet => :Resident&Animal {insuranceNumber :: INTEGER IS KEY, healthCertificate :: STRING IS UNIQUE, name :: STRING}),
    (:Robot => :Resident&Machine {application :: STRING NOT NULL, id :: INTEGER NOT NULL}),
    (:City => {name :: STRING NOT NULL, population :: INTEGER}),
-   (:Resident)-[:LIVES_IN => {since:: ANY NOT NULL}]->(:City),
+   (:Resident)-[:LIVES_IN => {since :: ANY NOT NULL}]->(:City),
    CONSTRAINT company_name FOR (c:Company) REQUIRE c.name IS KEY,
    CONSTRAINT resident_address FOR (resident:Resident) REQUIRE resident.address :: STRING,
    CONSTRAINT ownership_id FOR ()-[owner:OWNER_OF]->() REQUIRE owner.ownershipId IS UNIQUE,
    (:Company => {name :: STRING, address :: STRING IS UNIQUE}),
-   (:Person)-[:WORKS_FOR => {role :: STRING})->(:Company)
+   (:Person)-[:WORKS_FOR => {role :: STRING}]->(:Company)
 }
 ----
 
@@ -82,7 +82,7 @@ Dropping a node or relationship element type in this way can remove the followin
 
 These constraints cannot be removed separately from the node or relationship element type they support.
 
-Not allowed -- drop a dependent constraint from a node or relationship element type
+.Not allowed -- drop a dependent constraint from a node or relationship element type
 [source, cypher, role=test-fail]
 ----
 ALTER CURRENT GRAPH TYPE DROP {

modules/ROOT/pages/schema/graph-types/extend-graph-types.adoc

@@ -22,9 +22,9 @@ ALTER CURRENT GRAPH TYPE SET {
     (:Pet => :Resident&Animal {insuranceNumber :: INTEGER IS KEY, healthCertificate :: STRING IS UNIQUE, name :: STRING}),
     (:Robot => :Resident {application :: STRING NOT NULL}),
     (:City => {name :: STRING NOT NULL, population :: INTEGER}),
-    (:Resident)-[:LIVES_IN => {since:: DATE NOT NULL}]->(:City),
+    (:Resident)-[:LIVES_IN => {since :: DATE NOT NULL}]->(:City),
     CONSTRAINT company_name FOR (c:Company) REQUIRE c.name IS KEY,
-    CONSTRAINT animal_id FOR (a:Animal) REQUIRE a.Id IS UNIQUE,
+    CONSTRAINT animal_id FOR (a:Animal) REQUIRE a.id IS UNIQUE,
     CONSTRAINT resident_address FOR (resident:Resident) REQUIRE resident.address :: STRING
 }
 ----
@@ -90,25 +90,25 @@ The graph type now includes the added node and relationship element type:
 (:Pet => :Resident&Animal {insuranceNumber :: INTEGER IS KEY, healthCertificate :: STRING IS UNIQUE, name :: STRING}),
 (:Robot => Resident {application :: STRING NOT NULL}),
 (:City => {name :: STRING NOT NULL, population :: INTEGER}),
-(:Resident)-[:LIVES_IN => {since:: DATE NOT NULL}]->(:City),
+(:Resident)-[:LIVES_IN => {since :: DATE NOT NULL}]->(:City),
 CONSTRAINT company_name FOR (c:Company) REQUIRE c.name IS KEY,
-CONSTRAINT animal_id FOR (a:Animal) REQUIRE a.Id IS UNIQUE,
+CONSTRAINT animal_id FOR (a:Animal) REQUIRE a.id IS UNIQUE,
 CONSTRAINT resident_address FOR (resident:Resident) REQUIRE resident.address :: STRING,
 (:Company => {name :: STRING, address :: STRING IS UNIQUE}),
 (:Person)-[:WORKS_FOR => {role :: STRING}]->(:Company)
 ----
 
-.Updated graph type, showing added node element type and relationship element type
-image::graph-types-extend-graph-type.svg[Graph type showing added node element type and relationship element type, width=700, role=popup]
+.Updated data model, showing added node element type and relationship element type in graph type
+image::graph-types-extend-graph-type.svg[Updated data model showing added node element type and relationship element type, width=700, role=popup]
 
 .Invalid graph type extensions
 [source, cypher, role=test-fail]
 ----
 ALTER CURRENT GRAPH TYPE ADD {
-(p:Person => :Resident {name :: STRING, ssn :: INTEGER, nationality :: STRING})
-  REQUIRE (p.name, p.ssn) IS KEY, // <1>
-CONSTRAINT pet_address FOR (pet:Pet) REQUIRE pet.address IS NOT NULL, // <2>
-(:Animal => {type :: STRING NOT NULL}) // <3>
+  (p:Person => :Resident {name :: STRING, ssn :: INTEGER, nationality :: STRING})
+    REQUIRE (p.name, p.ssn) IS KEY, // <1>
+  CONSTRAINT pet_address FOR (pet:Pet) REQUIRE pet.address IS NOT NULL, // <2>
+  (:Animal => {type :: STRING NOT NULL}) // <3>
 }
 ----
 

modules/ROOT/pages/schema/graph-types/index.adoc

@@ -18,4 +18,4 @@ For more information about working with graph types, see:
 * xref:schema/graph-types/list-graph-types.adoc[]
 * xref:schema/graph-types/drop-graph-type-elements.adoc[]
 
-For reference material about the Cypher commands used to manage graph types, see xref:schema/syntax.adoc[].
+For reference material about the Cypher commands used to manage graph types, see xref:schema/syntax.adoc#graph-types[Syntax -> Graph types].