You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/errors/gql-errors.adoc
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ Status description:: error: connection exception - no such routing policy. Polic
98
98
99
99
== Invalid transaction state
100
100
101
-
Invalid transaction state errors occur when the client attempts to perform an operation that is not allowed in the current transaction state.
101
+
Invalid transaction state errors occur when the transaction is in an invalid state, such as when the transaction is terminated or closed, or when there is a conflict between the transaction state and applied updates.
102
102
103
103
=== 25N01
104
104
@@ -151,6 +151,8 @@ Status description:: error: invalid transaction state - cannot access entity aft
151
151
152
152
== Invalid transaction termination
153
153
154
+
Invalid transaction termination errors occur when the transaction termination fails, such as when the transaction or constituent transaction fails to commit, or when the transaction termination fails to apply or append the transaction.
155
+
154
156
=== 2DN01
155
157
156
158
Status description:: error: invalid transaction termination - commit failed. Failed to commit transaction. See debug log for details.
Transaction rollback errors occur when the transaction is rolled back due to an error, such as when the transaction rollback fails, or when the constituent rollback fails.
188
+
185
189
=== 40N01
186
190
187
191
Status description:: error: transaction rollback - rollback failed. Failed to rollback transaction. See debug log for details.
Syntax error or access rule violation errors occur when there is a syntax error in the query, or when the query violates the access rules, such as when the query contains an invalid syntax, or when the query tries to access a database that does not exist, etc.
201
+
202
+
=== 42I50
203
+
204
+
Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }`... A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`.
205
+
196
206
=== 42N01
197
207
198
208
Status description:: error: syntax error or access rule violation - no such constituent graph exists in composite database. The constituent graph { $graph } was not found in the in composite database { $db }. Verify that the spelling is correct.
@@ -293,10 +303,6 @@ Status description:: error: syntax error or access rule violation - invalid driv
293
303
294
304
Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }).
295
305
296
-
=== 42I50
297
-
298
-
Status description:: error: syntax error or access rule violation - token name too long. Invalid input { $input }. A { $tokenType } name cannot be longer than { $maxTokenLength }.
299
-
300
306
=== 42NFD
301
307
302
308
Status description:: error: syntax error or access rule violation - credentials expired. Permission denied. The credentials you provided were valid, but must be changed before you can use this instance.
0 commit comments