Skip to content

Commit e8393ce

Browse files
committed
apply suggestions from review
1 parent 3f6a5be commit e8393ce

File tree

1 file changed

+11
-5
lines changed

1 file changed

+11
-5
lines changed

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

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@ Status description:: error: data exception - invalid entity type. Invalid input
225225
226226
== Invalid transaction state
227227
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.
229229
230230
=== 25N01
231231
@@ -278,6 +278,8 @@ Status description:: error: invalid transaction state - cannot access entity aft
278278
279279
== Invalid transaction termination
280280
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+
281283
=== 2DN01
282284
283285
Status description:: error: invalid transaction termination - commit failed. Failed to commit transaction. See debug log for details.
@@ -309,6 +311,8 @@ Status description:: error: invalid transaction termination - inner transactions
309311
[[transaction-rollback]]
310312
== Transaction rollback
311313
314+
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+
312316
=== 40N01
313317
314318
Status description:: error: transaction rollback - rollback failed. Failed to rollback transaction. See debug log for details.
@@ -320,6 +324,12 @@ Status description:: error: transaction rollback - constituent rollback failed.
320324
[[syntax-error-access-rule-violation]]
321325
== Syntax error or access rule violation
322326
327+
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+
323333
=== 42N01
324334
325335
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
420430
421431
Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }).
422432
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-
427433
=== 42NFD
428434
429435
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

Comments
 (0)