Nested transactions: settings won't be resetted after inner Trx is done #3538
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
nPraml
changed the title
nPraml
changed the title
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.
Hello @rbygrave,
in our application we have a constellation that we use nested transactions (as in the testcase).
We switch on batchMode in the inner transaction, but unfortunately this also remains switched on for the outer transaction.
mariaDb cannot handle some prepared queries in the outer transaction and throws an exception in our use case.
We assumed that the settings in the nested transaction have no effect on the outer one. Do we assume this correctly?
Cheers
Noemi