Skip to content

Commit 58fbb09

Browse files
renetapopovaLojjs
andauthored
Add a warning that parsing status descriptions is not recommended (#228)
Co-authored-by: Louise Berglund <[email protected]>
1 parent 76b6273 commit 58fbb09

File tree

2 files changed

+11
-0
lines changed

2 files changed

+11
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,12 @@
77
The following page provides an overview of all GQLSTATUS server error codes in Neo4j.
88
All errors in Neo4j have severity level `ERROR`.
99

10+
[WARNING]
11+
====
12+
Please note that while GQLSTATUS codes remain stable, the status descriptions associated with these codes may change over time.
13+
For this reason, parsing the status descriptions or incorporating them into scripts is not recommended.
14+
====
15+
1016
== Connection exceptions
1117

1218
Connection exceptions occur when the client (e.g. Browser/Bloom/Cypher Shell) is unable to connect to the server for various reasons such as network issues, server-side routing being disabled, or the database being unavailable, etc.

modules/ROOT/pages/notifications/all-notifications.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,11 @@ The following page provides an overview of all notifications in Neo4j, including
1515
* <<_schema_notifications, `SCHEMA` notifications>>
1616
* <<_generic, `GENERIC` notifications>>
1717

18+
[WARNING]
19+
====
20+
Please note that while GQLSTATUS codes remain stable, the status descriptions associated with these codes may change over time.
21+
For this reason, parsing the status descriptions or incorporating them into scripts is not recommended.
22+
====
1823

1924
[#_performance_notifications]
2025
== `PERFORMANCE` notifications

0 commit comments

Comments
 (0)