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
@@ -225,7 +225,7 @@ Status description:: error: data exception - invalid entity type. Invalid input
225
225
226
226
== Invalid transaction state
227
227
228
-
Invalid transaction state errors occur when the client attempts to perform an operation that is not allowed in the current transaction state.
228
+
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.
229
229
230
230
=== 25N01
231
231
@@ -278,6 +278,8 @@ Status description:: error: invalid transaction state - cannot access entity aft
278
278
279
279
== Invalid transaction termination
280
280
281
+
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.
282
+
281
283
=== 2DN01
282
284
283
285
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.
315
+
312
316
=== 40N01
313
317
314
318
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.
328
+
329
+
=== 42I50
330
+
331
+
Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }`... A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`.
332
+
323
333
=== 42N01
324
334
325
335
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.
@@ -420,10 +430,6 @@ Status description:: error: syntax error or access rule violation - invalid driv
420
430
421
431
Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }).
422
432
423
-
=== 42I50
424
-
425
-
Status description:: error: syntax error or access rule violation - token name too long. Invalid input { $input }. A { $tokenType } name cannot be longer than { $maxTokenLength }.
426
-
427
433
=== 42NFD
428
434
429
435
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