fix: batch consecutive statements in runBatched#145
Merged
simolus3 merged 1 commit intoJun 4, 2026
Conversation
simolus3
previously approved these changes
Jun 4, 2026
shenlong-tanwen
force-pushed
the
fix/drift-batched-statements
branch
from
05a9795 to
98bd170
Compare
simolus3
approved these changes
Jun 4, 2026
Contributor
|
Released on pub.dev, thanks again for your contribution! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Previously
runBatchedissued onetx.executeper argument set, resulting in a sequential write for every row in a Drift batch. Instead, batch runs of consecutive arguments that share a statement index into a singletx.executeBatchcall, which is faster than the per-argument sequential write.