fix(client): Correctly execute batch transactions with single statement #17556
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
ab6c924 to
f052d9a
Compare
added 2 commits
February 2, 2023 11:48
When only a single request was executed within `$transaction`, it always got executed via singular request endpoint (and not batch). This endpoint is never run via transaction and cannot set isolation level. Fixed by forcing batch transaction requests to always go throu `requestBatch` endpoint. Fix #17555
56a7af9 to
be7c666
Compare
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 only a single request was executed within
$transaction, it alwaysgot executed via singular request endpoint (and not batch). This
endpoint is never run via transaction and cannot set isolation level.
Fixed by forcing batch transaction requests to always go throu
requestBatchendpoint.Fix #17555