Update RDB$TRANSACTION_STATE values #217
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks, it seems to have been documented wrong at least since the InterBase 6 Language Reference (page 268 in the PDF); I have verified against Firebird 1.5 and 2.5, and they also use 1 for limbo, 3 for rolled back (the method I used for testing results in committed transactions disappearing from RDB$TRANSACTIONS), and it's confirmed by the I'll also update the 2.5, 3.0 and 4.0 language references. |
|
I'll publish the changes to the site later today, and thanks for contributing! |
|
New version is published, but due to the cache, it might take a few hours to become visible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Firebird 5 I see these values for RDB$TRANSACTION_STATE in RDB$TRANSACTIONS table. Quick glance at source code confirms that.