Deprecate transaction nesting without savepoints #5383
Merged
+58
−0
Conversation
This file contains 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
greg0ire
force-pushed
the
deprecate-dummy-transac-behavior
branch
2 times, most recently
from
3832bfc to
73e3db6
Compare
When transaction nesting without savepoints is disabled, the behavior is suprising: there is no inner transaction, and the outer transaction is rolled back. Users relying on a platform that does not support savepoints will have to rework their application logic so as to avoid nested transaction blocks.
greg0ire
force-pushed
the
deprecate-dummy-transac-behavior
branch
from
73e3db6 to
b1437af
Compare
morozov
approved these changes
May 7, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When transaction nesting without savepoints is disabled, the behavior is
suprising: there is no inner transaction, and the outer transaction is
rolled back.
Users relying on a platform that does not support savepoints will have
to rework their application logic so as to avoid nested transaction
blocks.