Skip to content

Commit 8a2f848

Browse files
mnd999renetapopova
authored andcommitted
Error message updates from docs team review, these have been updated in the database code also.
1 parent ed31f3c commit 8a2f848

File tree

4 files changed

+13
-13
lines changed

4 files changed

+13
-13
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,12 @@ error: data exception - relationship element type is ineffectual. The relationsh
77
When defining a graph type, relationship element types must have some effect.
88
To be effective, a relationship element type must define at least one of the following:
99

10-
* A source node element type or label
11-
* A destination node element type or label
12-
* At least one property type
10+
* a source node element type or label
11+
* a destination node element type or label
12+
* at least one property type
1313

1414
== Example scenario
15-
For example, try to set a graph type with :
15+
For example, try to set a graph type as follows:
1616

1717
[source,cypher]
1818
----

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= 22NC4
22

33
== Status description
4-
error: data exception - a label cannot both identifying and implied. The label(s) `{ <<labelList>> }` are defined as both identifying and implied.
4+
error: data exception - a label cannot be both identifying and implied. The label(s) `{ <<labelList>> }` are defined as both identifying and implied.
55

66
== Explanation
77
When defining a graph type, labels and relationships must be assigned clear roles.
@@ -23,7 +23,7 @@ The query returns an error with GQLSTATUS 22NC4 and the status description:
2323

2424
[source]
2525
----
26-
error: data exception - a label cannot both identifying and implied. The label(s) `Person` are defined as both identifying and implied.
26+
error: data exception - a label cannot be both identifying and implied. The label(s) `Person` are defined as both identifying and implied.
2727
----
2828

2929
One way to fix this is to add another label to both nodes and capture the property type on `name` there:

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= 22NC5
22

33
== Status description
4-
error: data exception - graph type element not found. The `{ <<entityType>> }` element type referenced by `{ <<graphTypeReference>> }` was not found.
4+
error: data exception - graph type element not found. The `{ <<entityType>> }` element type referenced by `{ <<graphTypeReference>> }` does not exist.
55

66
== Explanation
77
This error occurs when a graph type definition references an element type (such as a node or relationship) using an alias that has not been defined, or by an identifying reference where there is no graph type element identified by that reference.
@@ -23,7 +23,7 @@ The query returns an error with GQLSTATUS 22NC5 and the status description:
2323

2424
[source]
2525
----
26-
error: data exception - graph type element not found. The node type element referenced by '(:Node =>)' was not found.
26+
error: data exception - graph type element not found. The node type element referenced by '(:Node =>)' does not exist.
2727
----
2828
In this case, you can make the reference to be non-identifying, or you can define the node type element before this operation:
2929

@@ -49,7 +49,7 @@ The query returns an error with GQLSTATUS 22NC5 and the status description:
4949

5050
[source]
5151
----
52-
error: data exception - graph type element not found. The relationship type element referenced by 'b' was not found.
52+
error: data exception - graph type element not found. The relationship type element referenced by 'b' does not exist.
5353
----
5454
In this case, the reference could be fixed by providing a relationship type:
5555

@@ -73,7 +73,7 @@ The query returns an error with GQLSTATUS 22NC5 and the status description:
7373

7474
[source]
7575
----
76-
error: data exception - graph type element not found. The node type element referenced by 'n' was not found.
76+
error: data exception - graph type element not found. The node type element referenced by 'n' was does not exist.
7777
----
7878
In this case, the reference can be fixed by providing a label for the constraint:
7979

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
= 22NC8
22

33
== Status description
4-
error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name `{ <<token>> }` more than once
4+
error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name `{ <<token>> }` more than once.more than once.
55

66
== Explanation
77
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.
@@ -26,7 +26,7 @@ The query returns an error with GQLSTATUS 22NC9 and the status description:
2626

2727
[source]
2828
----
29-
error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name 'p' more than once.
29+
error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name 'p' more than once.
3030
----
3131

3232
To fix this, rename one of the aliases, for example:
@@ -55,7 +55,7 @@ The query returns an error with GQLSTATUS 22NC9 and the status description:
5555

5656
[source]
5757
----
58-
error: data exception - graph type contains duplicated tokens. The graph type includes a label, relationship type or alias with name ':REL' more than once.
58+
error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name ':REL' more than once.
5959
----
6060

6161
To fix this, delete the duplicate relationship type definition, since they are both equivalent:

0 commit comments

Comments
 (0)