Skip to content

Commit ca3a596

Browse files
Fix constraints examples tests.
1 parent 8b6c28f commit ca3a596

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

modules/ROOT/pages/constraints/examples.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -369,7 +369,7 @@ It will be updated to say `Relationship property uniqueness constraints added: 1
369369
[[constraints-create-a-relationship-uniqueness-constraints-if-not-exist]]
370370
=== Handling existing constraints when creating a constraint
371371

372-
Creating an already existing constraint will fail.
372+
Creating an already existing constraint will fail.
373373
To avoid such an error, `IF NOT EXISTS` can be added to the `CREATE` command.
374374
This will ensure that no error is thrown and that no constraint is created if any other constraint with the given name, or another relationship property uniqueness constraint on the same schema, already exists.
375375

@@ -669,7 +669,7 @@ For the node property existence constraints, they will say `Node property existe
669669
[[constraints-create-a-node-property-existence-constraint-if-not-exist]]
670670
=== Handling existing constraints when creating a constraint
671671

672-
Creating an already existing constraint will fail.
672+
Creating an already existing constraint will fail.
673673
To avoid such an error, `IF NOT EXISTS` can be added to the `CREATE` command.
674674
This will ensure that no error is thrown and that no constraint is created if any other constraint with the given name, or another node property existence constraint on the same schema, already exists.
675675

@@ -905,7 +905,7 @@ For the relationship property existence constraints, they will say `Relationship
905905
[[constraints-create-a-relationship-property-existence-constraint-if-not-exist]]
906906
=== Handling existing constraints when creating a constraint
907907

908-
Creating an already existing constraint will fail.
908+
Creating an already existing constraint will fail.
909909
To avoid such an error, `IF NOT EXISTS` can be added to the `CREATE` command.
910910
This will ensure that no error is thrown and that no constraint is created if any other constraint with the given name, or another relationship property existence constraint on the same schema, already exists.
911911

@@ -1531,7 +1531,7 @@ Added 1 constraint.
15311531

15321532
[discrete]
15331533
[[constraints-create-a-relationship-property-type-constraint-union]]
1534-
=== Create a relationship property type constraint with a union type
1534+
=== Create a relationship property type constraint with a union type
15351535

15361536
_This feature was introduced in Neo4j 5.11._
15371537

@@ -1876,7 +1876,7 @@ Added 1 constraint.
18761876
[[constraints-create-a-node-key-constraint-if-not-exist]]
18771877
=== Handling existing constraints when creating a constraint
18781878

1879-
Creating an already existing constraint will fail.
1879+
Creating an already existing constraint will fail.
18801880
To avoid such an error, `IF NOT EXISTS` can be added to the `CREATE` command.
18811881
This will ensure that no error is thrown and that no constraint is created if any other constraint with the given name, or another node key constraint on the same schema, already exists.
18821882

@@ -2189,7 +2189,7 @@ Added 1 constraint.
21892189
[[constraints-create-a-relationship-key-constraint-if-not-exist]]
21902190
=== Handling existing constraints when creating a constraint
21912191

2192-
Creating an already existing constraint will fail.
2192+
Creating an already existing constraint will fail.
21932193
To avoid such an error, `IF NOT EXISTS` can be added to the `CREATE` command.
21942194
This will ensure that no error is thrown and that no constraint is created if any other constraint with the given name, or another relationship key constraint on the same schema, already exists.
21952195

@@ -2548,7 +2548,7 @@ This can be used to drop the constraint with the xref::constraints/syntax.adoc#c
25482548
======
25492549
25502550
.Query
2551-
[source, cypher]
2551+
[source, cypher, test-exclude-cols=id]
25522552
----
25532553
SHOW CONSTRAINTS
25542554
----
@@ -2576,7 +2576,7 @@ SHOW CONSTRAINTS
25762576
├────┼──────────────────────────────┼─────────────────────────────────┼──────────────┼───────────────┼────────────────────────────────┼───────────────────────────────┼─────────────────────────────────┤
25772577
│24 │"part_of" │"RELATIONSHIP_PROPERTY_TYPE" │"RELATIONSHIP"│["PART_OF"] │["order"] │null │"INTEGER" │
25782578
├────┼──────────────────────────────┼─────────────────────────────────┼──────────────┼───────────────┼────────────────────────────────┼───────────────────────────────┼─────────────────────────────────┤
2579-
│39 │"part_of_tags" │"RELATIONSHIP_PROPERTY_TYPE" │"RELATIONSHIP"│["PART_OF"] │["tags "] │null │"STRING | LIST<STRING NOT NULL>" │
2579+
│39 │"part_of_tags" │"RELATIONSHIP_PROPERTY_TYPE" │"RELATIONSHIP"│["PART_OF"] │["tags"] │null │"STRING | LIST<STRING NOT NULL>" │
25802580
├────┼──────────────────────────────┼─────────────────────────────────┼──────────────┼───────────────┼────────────────────────────────┼───────────────────────────────┼─────────────────────────────────┤
25812581
│30 │"preExisting_actor_name_age" │"UNIQUENESS" │"NODE" │["Actor"] │["firstname","age"] │"preExisting_actor_name_age" │null │
25822582
├────┼──────────────────────────────┼─────────────────────────────────┼──────────────┼───────────────┼────────────────────────────────┼───────────────────────────────┼─────────────────────────────────┤
@@ -2626,7 +2626,7 @@ An example is to only show constraints on relationships.
26262626
======
26272627
26282628
.Query
2629-
[source, cypher]
2629+
[source, cypher, test-exclude-cols=id]
26302630
----
26312631
SHOW EXISTENCE CONSTRAINTS
26322632
WHERE entityType = 'RELATIONSHIP'

0 commit comments

Comments
 (0)