-
Notifications
You must be signed in to change notification settings - Fork 35
Add 25, 2D, and 42 codes #191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
8f1199d
11875fe
3f6a5be
e8393ce
a6099ca
7b6b89f
d66edab
c189897
3151418
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,7 +12,7 @@ | |
| * <<_data-exceptions, Data exceptions>> | ||
|
|
||
| [[_connection-exceptions]] | ||
| ======= | ||
|
|
||
| >>>>>>> cf8ebb1 (Add 25, 2D, and 42 codes) | ||
| == Connection exceptions | ||
|
|
@@ -225,7 +225,7 @@ | |
|
|
||
| == Invalid transaction state | ||
|
|
||
| Invalid transaction state errors occur when the client attempts to perform an operation that is not allowed in the current transaction state. | ||
| 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. | ||
|
|
||
| === 25N01 | ||
|
|
||
|
|
@@ -278,6 +278,8 @@ | |
|
|
||
| == Invalid transaction termination | ||
|
|
||
| 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. | ||
|
|
||
| === 2DN01 | ||
|
|
||
| Status description:: error: invalid transaction termination - commit failed. Failed to commit transaction. See debug log for details. | ||
|
|
@@ -309,6 +311,8 @@ | |
| [[transaction-rollback]] | ||
| == Transaction rollback | ||
|
|
||
| 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. | ||
|
||
|
|
||
| === 40N01 | ||
|
|
||
| Status description:: error: transaction rollback - rollback failed. Failed to rollback transaction. See debug log for details. | ||
|
|
@@ -320,6 +324,12 @@ | |
| [[syntax-error-access-rule-violation]] | ||
| == Syntax error or access rule violation | ||
|
|
||
| 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. | ||
renetapopova marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| === 42I50 | ||
|
|
||
| Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }`... A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`. | ||
renetapopova marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| === 42N01 | ||
|
|
||
| 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 - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }). | ||
|
|
||
| === 42I50 | ||
|
|
||
| Status description:: error: syntax error or access rule violation - token name too long. Invalid input { $input }. A { $tokenType } name cannot be longer than { $maxTokenLength }. | ||
|
|
||
| === 42NFD | ||
|
|
||
| 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. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.