Add correction examples, scrap 22NC8

Author: mnd999

modules/ROOT/pages/errors/gql-errors/22NC1.adoc

@@ -23,6 +23,15 @@ An error will be thrown with GQLSTATUS 22NC1 and the status description:
 error: data exception - graph type element contains duplicated tokens. The graph type element includes a property key with name `prop` more than once.
 ----
 
+This can be corrected by removing the duplicate property key definition or naming the property keys uniquely:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Node => {prop :: STRING, prop2 :: INTEGER})
+}
+----
+
 ifndef::backend-pdf[]
 [discrete.glossary]
 == Glossary

modules/ROOT/pages/errors/gql-errors/22NC2.adoc

@@ -24,6 +24,15 @@ An error will be thrown with GQLSTATUS 22NC2 and the status description:
 error: data exception - node element type is empty. The node element type `Node` must contain one or more implied labels, or define at least one property type.
 ----
 
+This can be corrected by defining at least one property type or by adding an implied label e.g.:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (n:Node => { prop :: ANY NOT NULL })
+}
+----
+
 ifndef::backend-pdf[]
 [discrete.glossary]
 == Glossary

modules/ROOT/pages/errors/gql-errors/22NC3.adoc

@@ -24,6 +24,15 @@ An error will be thrown with GQLSTATUS 22NC3 and the status description:
 error: data exception - relationship element type is empty. The relationship element type `REL` must define a node element type for source or destination, or define at least one property type.
 ----
 
+This can be corrected by defining at least one property type or by adding a node element type e.g.:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ()-[:REL => {prop: ANY NOT NULL }]->()
+}
+----
+
 ifndef::backend-pdf[]
 [discrete.glossary]
 == Glossary

modules/ROOT/pages/errors/gql-errors/22NC4.adoc

@@ -26,6 +26,17 @@ An error will be thrown with GQLSTATUS 22NC4 and the status description:
 error: data exception - a label cannot both identifying and implied. The label(s) `Person` are defined as both identifying and implied.
 ----
 
+There are several ways to correct this, but one approch may be to add another label to both nodes and capture the property type on `name` there:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => :Named),
+    (s:Student => :Named),
+    CONSTRAINT FOR (:Named) REQUIRE name IS :: STRING
+}
+----
+
 ifndef::backend-pdf[]
 [discrete.glossary]
 == Glossary

modules/ROOT/pages/errors/gql-errors/22NC8.adoc

@@ -1,28 +1,70 @@
-= 22NC8
+= 22NC9
 
 == Status description
-error: data exception - constraint does not have a label or relationship type. The empty node type `()` is not a valid target for a constraint
+error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name `{ <<token>> }` more than once
 
 == Explanation
-This error occurs when you attempt to define a constraint on an empty node type.
-Constraints must target specific node types using a label.
-Using an empty node type means there is no label or type specified, which is not valid for constraint definitions.
+This error occurs when a graph type definition attempts to use the same name for more than one label, relationship type, or alias within the same scope.
+Each label, relationship type, or alias must have a unique name to avoid ambiguity in the graph schema.
+To resolve this error, ensure that all labels, relationship types, and aliases are uniquely named within the graph type definition.
 
-== Example scenario
-Attempt to define a constraint on an empty node reference as follows:
+== Example scenarios
+
+=== Aliases
+
+Attempt to define two node element types using the same alias.
 
 [source,cypher]
 ----
 ALTER CURRENT GRAPH TYPE SET {
-    CONSTRAINT FOR () REQUIRE n.badger IS UNIQUE
+  ( p: Person => { prop :: STRING } ),
+  ( p: Property => { prop :: STRING } )
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC8 and the status description:
+An error will be thrown with GQLSTATUS 22NC9 and the status description:
 
 [source]
 ----
-error: data exception - constraint does not have a label or relationship type. The empty node type `()` is not a valid target for a constraint.
+error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name 'p' more than once.
+----
+
+This can be corrected by renaming one of the aliases, for example:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  ( pers: Person => { prop :: STRING } ),
+  ( prop: Property => { prop :: STRING } )
+}
+----
+
+=== Identifiers
+
+Attempt to define two relationship element types using the same relationship type.
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  ()-[n:REL => { prop :: STRING }]->(),
+  ()-[m:REL => { prop :: STRING }]->()
+}
+----
+
+An error will be thrown with GQLSTATUS 22NC9 and the status description:
+
+[source]
+----
+error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name ':REL' more than once.
+----
+
+In this case, the correction is to delete the duplicate relationship type definition, since they are both equivalent:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  ()-[n:REL => { prop :: STRING }]->()
+}
 ----
 
 ifndef::backend-pdf[]

modules/ROOT/pages/errors/gql-errors/22NC9.adoc

@@ -1,52 +1,38 @@
-= 22NC9
+= 22NCA
 
 == Status description
-error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name `{ <<token>> }` more than once
+error: data exception - invalid element type constraints in graph type. A `{ <<entityType>> }` element type property `{ <<context>> }` constraint cannot be specified inline of a `{ <<entityType2>> }` element type
 
 == Explanation
-This error occurs when a graph type definition attempts to use the same name for more than one label, relationship type, or alias within the same scope.
-Each label, relationship type, or alias must have a unique name to avoid ambiguity in the graph schema.
-To resolve this error, ensure that all labels, relationship types, and aliases are uniquely named within the graph type definition.
+Property type and existance constrains cannot be defined as inline constraints on graph type elements.
+They should be defined as part of the property description instead.
 
-== Example scenarios
-
-=== Aliases
-
-Attempt to define two node element types using the same alias.
+== Example scenario
+Attempt to define an existance constraint inline of a node element type as follows:
 
 [source,cypher]
 ----
 ALTER CURRENT GRAPH TYPE SET {
-  ( p: Person => { prop :: STRING } ),
-  ( p: Property => { prop :: STRING } )
+    (p:Person => {name :: STRING, age :: INT}) REQUIRE p.studId IS NOT NULL
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC9 and the status description:
+An error will be thrown with GQLSTATUS 22NCA and the status description:
 
 [source]
 ----
-error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name 'p' more than once.
+error: data exception - invalid element type constraints in graph type. A node element type property existence constraint cannot be specified inline of a node element type.
 ----
 
-=== Identifiers
+A correct definition is as follows:
 
-Attempt to define two relationship element types using the same relationship type.
-
-[source,cypher]
+[source, cypher]
 ----
 ALTER CURRENT GRAPH TYPE SET {
-  ()-[n:REL => { prop :: STRING }]->(),
-  ()-[m:REL => { prop :: STRING }]->()
+    (p :Person => {name :: STRING, age :: INT, studId :: ANY NOT NULL })
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC9 and the status description:
-
-[source]
-----
-error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name ':REL' more than once.
-----
 
 ifndef::backend-pdf[]
 [discrete.glossary]