up to set graph type on a populated database

Author: JPryce-Aklundh

modules/ROOT/content-nav.adoc

@@ -115,9 +115,10 @@
 *** xref:indexes/semantic-indexes/vector-indexes.adoc[]
 ** xref:indexes/syntax.adoc[]
 
-* xref:constraints/index.adoc[]
-** xref:constraints/managing-constraints.adoc[]
-** xref:constraints/syntax.adoc[]
+* xref:schema/index.adoc[]
+** xref:schema/graph-types.adoc[]
+** xref:schema/constraints.adoc[]
+** xref:schema/syntax.adoc[]
 
 * xref:planning-and-tuning/index.adoc[]
 ** xref:planning-and-tuning/execution-plans.adoc[]

modules/ROOT/images/graph-types-data-in-database.svg

@@ -616,16 +616,16 @@ GQL supports `GRAPH TYPES` as a way of constraining a graph schema, but does not
 | Cypher feature
 | Description
 
-| xref:constraints/managing-constraints.adoc#create-property-uniqueness-constraints[Property uniqueness constraints]
+| xref:schema/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/managing-constraints.adoc#create-property-existence-constraints[Property existence constraints]
+| xref:schema/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/managing-constraints.adoc#create-property-type-constraints[Property type constraints]
+| xref:schema/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/managing-constraints.adoc#create-key-constraints[Key constraints]
+| xref:schema/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/images/graph-types-data-model.svg

@@ -936,7 +936,7 @@ Predicates that will not work:
 
 [NOTE]
 ====
-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.
+If there is a xref:schema/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`
 
 Predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.

modules/ROOT/images/graph-types-element-type-constraints.svg

@@ -142,9 +142,9 @@ DETACH DELETE n
 Deleted 3 nodes, deleted 1 relationship
 ----
 
-`DETACH DELETE` is useful when experimenting with small example datasets, but it is not suitable for deleting large amounts of data, nor does it delete xref:indexes/search-performance-indexes/index.adoc[indexes] and xref:constraints/index.adoc[constraints].
+`DETACH DELETE` is useful when experimenting with small example datasets, but it is not suitable for deleting large amounts of data, nor does it delete xref:indexes/search-performance-indexes/index.adoc[indexes] or any xref:schema/index.adoc[schema].
 
-To delete large amounts of data without deleting indexes and constraints, use xref::subqueries/subqueries-in-transactions.adoc#delete-with-call-in-transactions[CALL subqueries in transactions] instead.
+To delete large amounts of data without deleting indexes and any schema, use xref::subqueries/subqueries-in-transactions.adoc#delete-with-call-in-transactions[CALL subqueries in transactions] instead.
 
 .Delete all nodes and relationships using `CALL` subqueries
 [source, cypher]

modules/ROOT/images/graph-types-node-element-type.svg

@@ -278,7 +278,7 @@ These comprise clauses to create, show, and drop indexes and constraints.
 m| xref:indexes/syntax.adoc[CREATE \| SHOW  \| DROP INDEX]
 | Create, show or drop an index.
 
-m| xref::constraints/syntax.adoc[CREATE \| SHOW \| DROP CONSTRAINT]
+m| xref::schema/syntax.adoc[CREATE \| SHOW \| DROP CONSTRAINT]
 | Create, show or drop a constraint.
 |===