Re-add relationship constraint documentation (#490)

Companion PR to neo4j/docs-cheat-sheet#69

Author: Hunterness

modules/ROOT/pages/constraints/examples.adoc

@@ -18,13 +18,10 @@ Unique node property constraints, or node property uniqueness constraints, ensur
 For property uniqueness constraints on multiple properties, the combination of the property values is unique.
 Node property uniqueness constraints do not require all nodes to have a unique value for the properties listed (nodes without all properties are not subject to this rule).
 
-// TODO: Re-add this part when adding back relationship key and uniqueness constraints
-////
 *Unique relationship property constraints*::
 Unique relationship property constraints, or relationship property uniqueness constraints, ensure that property values are unique for all relationships with a specific type.
 For property uniqueness constraints on multiple properties, the combination of the property values is unique.
 Relationship property uniqueness constraints do not require all relationships to have a unique value for the properties listed (relationships without all properties are not subject to this rule).
-////
 
 *Node property existence constraints* label:enterprise-edition[]::
 Node property existence constraints ensure that a property exists for all nodes with a specific label.
@@ -50,8 +47,6 @@ Queries attempting to do any of the following will fail:
 * Remove one of the mandatory properties.
 * Update the properties so that the combination of property values is no longer unique.
 
-// TODO: Re-add this part when adding back relationship key and uniqueness constraints
-////
 *Relationship key constraints* label:enterprise-edition[]::
 Relationship key constraints ensure that, for a given type and set of properties:
 +
@@ -65,14 +60,11 @@ Queries attempting to do any of the following will fail:
 * Create new relationships without all the properties or where the combination of property values is not unique.
 * Remove one of the mandatory properties.
 * Update the properties so that the combination of property values is no longer unique.
-////
 
 
 [NOTE]
 ====
-Node key constraints, node property existence constraints, and relationship property existence constraints are only available in Neo4j Enterprise Edition.
-// TODO: Switch the row above to the one below when adding back relationship key and uniqueness constraints
-//Node key constraints, relationship key constraints, node property existence constraints, and relationship property existence constraints are only available in Neo4j Enterprise Edition.
+Node key constraints, relationship key constraints, node property existence constraints, and relationship property existence constraints are not available in Neo4j Community Edition.
 Databases containing one of these constraint types cannot be opened using Neo4j Community Edition.
 ====
 
@@ -81,26 +73,15 @@ Databases containing one of these constraint types cannot be opened using Neo4j
 
 Creating a constraint has the following implications on indexes:
 
-* Adding a node key or property uniqueness constraint on a single property also adds an index on that property, and therefore, an index of the same index type, label, and property combination cannot be added separately.
-* Adding a node key or property uniqueness constraint for a set of properties also adds an index on those properties, and therefore, an index of the same index type, label, and properties combination cannot be added separately.
-* Cypher will use these indexes for lookups just like other indexes.
-  Refer to xref::indexes-for-search-performance.adoc[] for more details on indexes.
-* If a node key or property uniqueness constraint is dropped and the backing index is still required, the index need to be created explicitly.
-
-////
-TODO: Switch the part above to the one below when adding back relationship key and uniqueness constraints
 * Adding a node key, relationship key, or property uniqueness constraint on a single property also adds an index on that property, and therefore, an index of the same index type, label/relationship type, and property combination cannot be added separately.
 * Adding a node key, relationship key, or property uniqueness constraint for a set of properties also adds an index on those properties, and therefore, an index of the same index type, label/relationship type, and properties combination cannot be added separately.
 * Cypher will use these indexes for lookups just like other indexes.
   Refer to xref::indexes-for-search-performance.adoc[] for more details on indexes.
 * If a node key, relationship key, or property uniqueness constraint is dropped and the backing index is still required, the index need to be created explicitly.
-////
 
 Additionally, the following is true for constraints:
 
-* A given label can have multiple constraints, and uniqueness and property existence constraints can be combined on the same property.
-// TODO: Switch the row above to the one below when adding back relationship key and uniqueness constraints
-//* A given label or relationship type can have multiple constraints, and uniqueness and property existence constraints can be combined on the same property.
+* A given label or relationship type can have multiple constraints, and uniqueness and property existence constraints can be combined on the same property.
 * Adding constraints is an atomic operation that can take a while -- all existing data has to be scanned before Neo4j DBMS can turn the constraint 'on'.
 * Best practice is to give the constraint a name when it is created.
 If the constraint is not explicitly named, it will get an auto-generated name.

modules/ROOT/pages/constraints/index.adoc

@@ -56,8 +56,6 @@ REQUIRE (n.propertyName_1, ..., n.propertyName_n) IS [NODE] UNIQUE
 Index provider can be specified using the `OPTIONS` clause.
 
 
-////
-TODO: Re-add this part when adding back relationship key and uniqueness constraints
 [[constraints-syntax-create-rel-unique]]
 [discrete]
 === Create a relationship property uniqueness constraint
@@ -81,7 +79,6 @@ REQUIRE (r.propertyName_1, ..., r.propertyName_n) IS [REL[ATIONSHIP]] UNIQUE
 ----
 
 Index provider can be specified using the `OPTIONS` clause.
-////
 
 
 [[constraints-syntax-create-node-exists]]
@@ -149,8 +146,6 @@ REQUIRE (n.propertyName_1, ..., n.propertyName_n) IS [NODE] KEY
 Index provider can be specified using the `OPTIONS` clause.
 
 
-////
-TODO: Re-add this part when adding back relationship key and uniqueness constraints
 [[constraints-syntax-create-rel-key]]
 [discrete]
 === Create a relationship key constraint label:enterprise-edition[]
@@ -174,7 +169,6 @@ REQUIRE (r.propertyName_1, ..., r.propertyName_n) IS [REL[ATIONSHIP]] KEY
 ----
 
 Index provider can be specified using the `OPTIONS` clause.
-////
 
 
 [[constraints-syntax-drop]]
@@ -208,21 +202,6 @@ Listing constraints requires the xref::administration/access-control/database-ad
 
 The simple version of the command allows for a `WHERE` clause and will give back the default set of output columns:
 
-[source, syntax, role="noheader", indent=0]
-----
-SHOW [
-      ALL
-     |UNIQUE[NESS]
-     |NODE [PROPERTY] EXIST[ENCE]
-     |REL[ATIONSHIP] [PROPERTY] EXIST[ENCE]
-     |[PROPERTY] EXIST[ENCE]
-     |NODE KEY
-] CONSTRAINT[S]
-  [WHERE expression]
-----
-
-////
-TODO: Switch the syntax above to the one below when adding back relationship key and uniqueness constraints
 [source, syntax, role="noheader", indent=0]
 ----
 SHOW [
@@ -239,27 +218,9 @@ SHOW [
 ] CONSTRAINT[S]
   [WHERE expression]
 ----
-////
 
 To get the full set of output columns, a yield clause is needed:
 
-[source, syntax, role="noheader", indent=0]
-----
-SHOW [
-      ALL
-     |UNIQUE[NESS]
-     |NODE [PROPERTY] EXIST[ENCE]
-     |REL[ATIONSHIP] [PROPERTY] EXIST[ENCE]
-     |[PROPERTY] EXIST[ENCE]
-     |NODE KEY
-] CONSTRAINT[S]
-YIELD { * | field[, ...] } [ORDER BY field[, ...]] [SKIP n] [LIMIT n]
-  [WHERE expression]
-  [RETURN field[, ...] [ORDER BY field[, ...]] [SKIP n] [LIMIT n]]
-----
-
-////
-TODO: Switch the syntax above to the one below when adding back relationship key and uniqueness constraints
 [source, syntax, role="noheader", indent=0]
 ----
 SHOW [
@@ -278,7 +239,6 @@ YIELD { * | field[, ...] } [ORDER BY field[, ...]] [SKIP n] [LIMIT n]
   [WHERE expression]
   [RETURN field[, ...] [ORDER BY field[, ...]] [SKIP n] [LIMIT n]]
 ----
-////
 
 
 The type filtering keywords filters the returned constraints on constraint type:
@@ -293,18 +253,14 @@ The type filtering keywords filters the returned constraints on constraint type:
 | Returns all constraints, no filtering on constraint type.
 This is the default if none is given.
 
-// TODO: Re-add these parts when adding back relationship key and uniqueness constraints
-//|NODE UNIQUE[NESS]
-//| Returns the node property uniqueness constraints.
+|NODE UNIQUE[NESS]
+| Returns the node property uniqueness constraints.
 
-//|REL[ATIONSHIP] UNIQUE[NESS]
-//| Returns the relationship property uniqueness constraints.
+|REL[ATIONSHIP] UNIQUE[NESS]
+| Returns the relationship property uniqueness constraints.
 
 |UNIQUE[NESS]
-| Returns all property uniqueness constraints.
-// TODO: Switch the part above to the one below when adding back relationship key and uniqueness constraints
-//|UNIQUE[NESS]
-//| Returns all property uniqueness constraints, for both nodes and relationships.
+| Returns all property uniqueness constraints, for both nodes and relationships.
 
 |NODE [PROPERTY] EXIST[ENCE]
 | Returns the node property existence constraints.
@@ -318,12 +274,11 @@ This is the default if none is given.
 |NODE KEY
 | Returns the node key constraints.
 
-// TODO: Re-add these parts when adding back relationship key and uniqueness constraints
-//|REL[ATIONSHIP] KEY
-//| Returns the relationship key constraints.
+|REL[ATIONSHIP] KEY
+| Returns the relationship key constraints.
 
-//|KEY
-//| Returns all node and relationship key constraints.
+|KEY
+| Returns all node and relationship key constraints.
 
 |===
 
@@ -344,9 +299,7 @@ The returned columns from the show command is:
 | STRING
 
 | type
-| The ConstraintType of this constraint (`UNIQUENESS`, `NODE_PROPERTY_EXISTENCE`, `RELATIONSHIP_PROPERTY_EXISTENCE`, or `NODE_KEY`). label:default-output[]
-// TODO: Switch the row above to the one below when adding back relationship key and uniqueness constraints
-//| The ConstraintType of this constraint (`UNIQUENESS` (node uniqueness), `RELATIONSHIP_UNIQUENESS`, `NODE_PROPERTY_EXISTENCE`, `RELATIONSHIP_PROPERTY_EXISTENCE`, `NODE_KEY`, or `RELATIONSHIP_KEY`). label:default-output[]
+| The ConstraintType of this constraint (`UNIQUENESS` (node uniqueness), `RELATIONSHIP_UNIQUENESS`, `NODE_PROPERTY_EXISTENCE`, `RELATIONSHIP_PROPERTY_EXISTENCE`, `NODE_KEY`, or `RELATIONSHIP_KEY`). label:default-output[]
 | STRING
 
 | entityType

modules/ROOT/pages/constraints/syntax.adoc

@@ -36,6 +36,7 @@ a|
 
 The Cypher query option `connectComponentsPlanner` is deprecated and will be removed without a replacement.
 The product's default behavior of using a cost-based IDP search algorithm when combining sub-plans will be kept.
+
 |===
 
 
@@ -54,8 +55,44 @@ label:updated[]
 ALTER DATABASE ... [WAIT [n [SEC[OND[S]]]]\|NOWAIT]
 ----
 a|
-New sub-clause `WAIT` for `ALTER DATABASE`. 
-This enables adding a waiting clause to specify a time limit in which the command must be completed and returned. 
+New sub-clause `WAIT` for `ALTER DATABASE`.
+This enables adding a waiting clause to specify a time limit in which the command must be completed and returned.
+
+a|
+label:functionality[]
+label:new[]
+[source, cypher, role="noheader"]
+----
+CREATE CONSTRAINT name FOR ()-[r:TYPE]-() REQUIRE r.prop IS UNIQUE
+
+CREATE CONSTRAINT name FOR ()-[r:TYPE]-() REQUIRE r.prop IS RELATIONSHIP KEY
+----
+a|
+
+Added relationship xref:constraints/syntax.adoc#constraints-syntax-create-rel-key[key] and xref:constraints/syntax.adoc#constraints-syntax-create-rel-unique[uniqueness] constraints.
+
+a|
+label:functionality[]
+label:new[]
+[source, cypher, role="noheader"]
+----
+SHOW NODE UNIQUE[NESS] CONSTRAINTS
+
+SHOW REL[ATIONSHIP] UNIQUE[NESS] CONSTRAINTS
+
+SHOW UNIQUE[NESS] CONSTRAINTS
+
+SHOW REL[ATIONSHIP] KEY CONSTRAINTS
+
+SHOW KEY CONSTRAINTS
+----
+a|
+
+Added filtering for the new constraint types to `SHOW CONSTRAINTS`.
+Includes filtering for the node part, relationship part, or both parts of each type (`NODE KEY` filtering already exists previously).
+
+The existing `UNIQUENESS` filter will now return both node and relationship property uniqueness constraints.
+
 |===
 
 [[cypher-deprecations-additions-removals-5.6]]
@@ -164,32 +201,6 @@ RETURN 'val' as one, 'val' as two
 [[cypher-deprecations-additions-removals-5.3]]
 == Version 5.3
 
-// TODO: Re-add this part in whatever version (not 5.3...) the relationship key and uniqueness constraints are added back in
-////
-=== Deprecated features
-
-[cols="2", options="header"]
-|===
-| Feature
-| Details
-
-a|
-//not sure what category this should be, it is more information about a coming breaking change than actual deprecation
-label:returnValues[]
-label:deprecated[]
-[source, cypher, role="noheader"]
-----
-SHOW NODE UNIQUENESS CONSTRAINTS YIELD type
-----
-a|
-
-The current constraint type for node property uniqueness constraints, `UNIQUENESS`, will be updated to `NODE_UNIQUENESS` in Neo4j version 6.0.
-
-This will also be reflected in updates to some error messages and query statistics.
-
-|===
-////
-
 === Updated features
 
 [cols="2", options="header"]
@@ -252,53 +263,6 @@ The property uniqueness constraint type filter now allow both `UNIQUE` and `UNIQ
 
 |===
 
-// TODO: Re-add this part in whatever version (not 5.3...) the relationship key and uniqueness constraints are added back in
-////
-=== New features
-
-[cols="2", options="header"]
-|===
-| Feature
-| Details
-
-a|
-label:functionality[]
-label:new[]
-[source, cypher, role="noheader"]
-----
-CREATE CONSTRAINT name FOR ()-[r:TYPE]-() REQUIRE r.prop IS UNIQUE
-
-CREATE CONSTRAINT name FOR ()-[r:TYPE]-() REQUIRE r.prop IS RELATIONSHIP KEY
-----
-a|
-
-Added relationship xref:constraints/syntax.adoc#constraints-syntax-create-rel-key[key] and xref:constraints/syntax.adoc#constraints-syntax-create-rel-unique[uniqueness] constraints.
-
-a|
-label:functionality[]
-label:new[]
-[source, cypher, role="noheader"]
-----
-SHOW NODE UNIQUE[NESS] CONSTRAINTS
-
-SHOW REL[ATIONSHIP] UNIQUE[NESS] CONSTRAINTS
-
-SHOW UNIQUE[NESS] CONSTRAINTS
-
-SHOW REL[ATIONSHIP] KEY CONSTRAINTS
-
-SHOW KEY CONSTRAINTS
-----
-a|
-
-Added filtering for the new constraint types to `SHOW CONSTRAINTS`.
-Includes filtering for the node part, relationship part, or both parts of each type (`NODE KEY` filtering already exists previously).
-
-The existing `UNIQUENESS` filter will now return both node and relationship property uniqueness constraints.
-
-|===
-////
-
 [[cypher-deprecations-additions-removals-5.2]]
 == Version 5.2
 

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

@@ -5022,9 +5022,7 @@ This constraint can have any of the available constraint types:
 
 * Property uniqueness constraints
 * Property existence constraints label:enterprise-edition[]
-* Node key constraints label:enterprise-edition[]
-// TODO: Switch the row above to the one below when adding back relationship key and uniqueness constraints
-//* Node or relationship key constraints label:enterprise-edition[]
+* Node or relationship key constraints label:enterprise-edition[]
 
 The following query will create a property uniqueness constraint with the name `uniqueness` on the `name` property of nodes with the `Country` label.
 

modules/ROOT/pages/execution-plans/operators.adoc

@@ -32,22 +32,12 @@ a|
 All constraints:
 xref::constraints/examples.adoc#constraints-examples-node-property-existence[node existence constraints],
 xref::constraints/examples.adoc#constraints-examples-relationship-property-existence[relationship existence constraints],
-xref::constraints/examples.adoc#constraints-examples-node-uniqueness[node property uniqueness constraints], and
-xref::constraints/examples.adoc#constraints-examples-node-key[node key constraints].
-////
-TODO: Switch the part above to the one below when adding back relationship key and uniqueness constraints
-All constraints:
-xref::constraints/examples.adoc#constraints-examples-node-property-existence[node existence constraints],
-xref::constraints/examples.adoc#constraints-examples-relationship-property-existence[relationship existence constraints],
 xref::constraints/examples.adoc#constraints-examples-node-uniqueness[node property uniqueness constraints],
 xref::constraints/examples.adoc#constraints-examples-relationship-uniqueness[relationship property uniqueness constraints],
 xref::constraints/examples.adoc#constraints-examples-node-key[node key constraints], and
 xref::constraints/examples.adoc#constraints-examples-relationship-key[relationship key constraints].
-////
 a|
-Only xref::constraints/examples.adoc#constraints-examples-node-uniqueness[node property uniqueness constraints].
-// TODO: Switch the row above to the one below when adding back relationship key and uniqueness constraints
-//Only xref::constraints/examples.adoc#constraints-examples-node-uniqueness[node] and xref::constraints/examples.adoc#constraints-examples-relationship-uniqueness[relationship] property uniqueness constraints.
+Only xref::constraints/examples.adoc#constraints-examples-node-uniqueness[node] and xref::constraints/examples.adoc#constraints-examples-relationship-uniqueness[relationship] property uniqueness constraints.
 
 |===