Skip to content

Commit 3539a61

Browse files
committed
apply suggestions from review
1 parent ba5a9bf commit 3539a61

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
@@ -98,7 +98,7 @@ Status description:: error: connection exception - no such routing policy. Polic
9898

9999
== Invalid transaction state
100100

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.
102102

103103
=== 25N01
104104

@@ -151,6 +151,8 @@ Status description:: error: invalid transaction state - cannot access entity aft
151151

152152
== Invalid transaction termination
153153

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+
154156
=== 2DN01
155157

156158
Status description:: error: invalid transaction termination - commit failed. Failed to commit transaction. See debug log for details.
@@ -182,6 +184,8 @@ Status description:: error: invalid transaction termination - inner transactions
182184
[[transaction-rollback]]
183185
== Transaction rollback
184186

187+
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+
185189
=== 40N01
186190

187191
Status description:: error: transaction rollback - rollback failed. Failed to rollback transaction. See debug log for details.
@@ -193,6 +197,12 @@ Status description:: error: transaction rollback - constituent rollback failed.
193197
[[syntax-error-access-rule-violation]]
194198
== Syntax error or access rule violation
195199

200+
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+
196206
=== 42N01
197207

198208
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
293303

294304
Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }).
295305

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-
300306
=== 42NFD
301307

302308
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)