Add connection exception errors #183
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renetapopova
changed the title
Lojjs
reviewed
Oct 11, 2024
renetapopova
force-pushed
the
standard-defined-connection-exceptions
branch
from
c8cc746 to
87645d8
Compare
renetapopova
changed the title
Lojjs
reviewed
Oct 15, 2024
Comment on lines
+96
to
+114
| === Standard-defined GQLSTATUS notification codes | ||
|
|
||
| The GQL standard defines a set of GQLSTATUS codes that are used to represent successful completion, warnings, and informational messages. | ||
| The following table lists the standard-defined GQLSTATUS codes and their meanings: | ||
|
|
||
| .Standard-defined GQLSTATUS notification codes | ||
| [options="header", cols="<1s,<4"] | ||
| |=== | ||
| |GQLSTATUS code | StatusDescription | ||
| | 00000 | note: successful completion | ||
| | 00001 | note: successful completion - omitted result | ||
| | 01000 | warn: warning | ||
| | 01004 | warn: string data, right truncation | ||
| | 01G03 | warn: graph does not exist | ||
| | 01G04 | warn: graph type does not exist | ||
| | 01G11 | warn: null value eliminated in set function | ||
| | 02000 | note: no data | ||
| | 03000 | info: informational | ||
| |=== |
There was a problem hiding this comment.
I can't remember what we said about this, should we keep it or not? I'm open for either, we can always revisit later.
There was a problem hiding this comment.
I think it makes sense for notifications, as the list is short, and it looks good in the structure, but I also don't have a strong opinion. Should I create a card to change the format of the notification parameters?
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Lojjs
approved these changes
Oct 15, 2024
renetapopova
added a commit
that referenced
this pull request
Oct 31, 2024
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
renetapopova
added a commit
to renetapopova/docs-status-codes
that referenced
this pull request
Oct 31, 2024
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.