Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add codes starting with 42 #196

Merged
merged 18 commits into from
Oct 25, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 18 additions & 18 deletions modules/ROOT/pages/errors/gql-errors.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ Status description:: error: data exception - invalid spatial value. A POINT must

=== 22N20

Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with `{ $dim1 }D coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D coordinate reference system instead.
Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with `{ $dim1 }D` coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D` coordinate reference system instead.

=== 22N21

Expand Down Expand Up @@ -387,7 +387,7 @@ Status description:: error: syntax error or access rule violation - invalid case

=== 42I01

Status description:: error: syntax error or access rule violation - invalid FOREACH. Invalid use of `{ $clause }` inside 'FOREACH'.
Status description:: error: syntax error or access rule violation - invalid `FOREACH`. Invalid use of `{ $clause }` inside 'FOREACH'.

=== 42I02

Expand All @@ -408,36 +408,36 @@ Status description:: error: syntax error or access rule violation - invalid symb

=== 42I25

Status description:: error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS. 'CALL { ... }` IN TRANSACTIONS' is not supported after a write clause.
Status description:: error: syntax error or access rule violation - invalid use of `CALL IN TRANSACTIONS`. 'CALL { ... } IN TRANSACTIONS' is not supported after a write clause.

=== 42I29

Status description:: error: syntax error or access rule violation - invalid use of IS. The IS keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
Status description:: error: syntax error or access rule violation - invalid use of `IS`. The `IS` keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.

=== 42I31

Status description:: error: syntax error or access rule violation - invalid use of MATCH. MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
Status description:: error: syntax error or access rule violation - invalid use of `MATCH`. 'MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a `WITH` clause between them.


=== 42I37

Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. `RETURN *'` is not allowed when there are no variables in scope.
Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. 'RETURN *' is not allowed when there are no variables in scope.

=== 42I38

Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. `RETURN ...'` can only be used at the end of a query or subquery.
Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. 'RETURN ...' can only be used at the end of a query or subquery.

=== 42I40

Status description:: error: syntax error or access rule violation - invalid use of `UNION and UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
Status description:: error: syntax error or access rule violation - invalid use of `UNION` and `UNION ALL`. `UNION` and `UNION ALL` cannot be combined.

=== 42I47

Status description:: error: syntax error or access rule violation - parser error. Parser Error: `{ $msg }`.

=== 42I50

Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }`... A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`.
Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }..`. A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure about putting the backticks in between the dots on this one. I guess the dots are supposed to be ... like in etc. but also they are in the end of a sentence. I leave it up to you, how you think it is best to format

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was also not sure about this one. As I understood Emelie, the dots here mean that the displayed input is truncated. But the last dot should be a full stop, in my opinion; otherwise, the sentence will look unfinished. 🤷

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was thinking the same way, let's keep it like this and change it later if someone would complain (which I doubt)


=== 42N00

Expand All @@ -453,7 +453,7 @@ Status description:: error: syntax error or access rule violation - writing in r

=== 42N03

Status description:: error: syntax error or access rule violation - writing to multiple graphs. Writing to multiple graphs in the same transaction is not allowed. Use CALL IN TRANSACTION or create separate transactions in your application.
Status description:: error: syntax error or access rule violation - writing to multiple graphs. Writing to multiple graphs in the same transaction is not allowed. Use `CALL IN TRANSACTION` or create separate transactions in your application.

=== 42N04

Expand Down Expand Up @@ -485,7 +485,7 @@ Status description:: error: syntax error or access rule violation - no such role

=== 42N11

Status description:: error: syntax error or access rule violation - database or alias already exists. A [composite] database or alias with the name `{ $db }` already exists.
Status description:: error: syntax error or access rule violation - database or alias already exists. A `[composite]` database or alias with the name `{ $db }` already exists.

=== 42N12

Expand Down Expand Up @@ -517,7 +517,7 @@ Status description:: error: syntax error or access rule violation - duplicate cl

=== 42N20

Status description:: error: syntax error or access rule violation - empty list range operator. The list range operator `'[ ]'` cannot be empty.
Status description:: error: syntax error or access rule violation - empty list range operator. The list range operator '[ ]' cannot be empty.


=== 42N21
Expand All @@ -527,15 +527,15 @@ Status description:: error: syntax error or access rule violation - unaliased re

=== 42N22

Status description:: error: syntax error or access rule violation - single return column required. A COLLECT subquery must end with a single return column.
Status description:: error: syntax error or access rule violation - single return column required. A `COLLECT` subquery must end with a single return column.

=== 42N29

Status description:: error: syntax error or access rule violation - unbound variables in pattern expression. Pattern expressions are not allowed to introduce new variables: `{ $var }`.
renetapopova marked this conversation as resolved.
Show resolved Hide resolved

=== 42N39

Status description:: error: syntax error or access rule violation - incompatible return columns. All subqueries in a UNION clause must have the same return column names.
Status description:: error: syntax error or access rule violation - incompatible return columns. All subqueries in a `UNION` clause must have the same return column names.

=== 42N45

Expand All @@ -555,7 +555,7 @@ Status description:: error: syntax error or access rule violation - function wit

=== 42N75

Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function `{ $fun }` is only allowed as the top-level argument of a USE clause.
Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function `{ $fun }` is only allowed as the top-level argument of a `USE` clause.

=== 42N76

Expand All @@ -572,7 +572,7 @@ Status description:: error: syntax error or access rule violation - impersonatio

=== 42N84

Status description:: error: syntax error or access rule violation - TERMINATE TRANSACTION misses YIELD clause. WHERE clause without YIELD clause. Use 'TERMINATE TRANSACTION ... YIELD ... WHERE ...'.
Status description:: error: syntax error or access rule violation - `TERMINATE TRANSACTION` misses `YIELD` clause. `WHERE` clause without `YIELD` clause. Use 'TERMINATE TRANSACTION ... YIELD ... WHERE ...'.

=== 42N85

Expand All @@ -588,11 +588,11 @@ Status description:: error: syntax error or access rule violation - cannot grant

=== 42N89

Status description:: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. `{ $cause }
Status description:: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. { $cause }

=== 42N90

Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: `{ $db }).
Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: `{ $db }`).

=== 42N97

Expand Down