Skip to content

fix(drizzle): size sqlite batch inserts by widest row - #17234

Open
r1tsuu wants to merge 1 commit into
mainfrom
fix/sqlite-batch-insert-params-per-row
Open

fix(drizzle): size sqlite batch inserts by widest row#17234
r1tsuu wants to merge 1 commit into
mainfrom
fix/sqlite-batch-insert-params-per-row

Conversation

@r1tsuu

@r1tsuu r1tsuu commented Jul 8, 2026

Copy link
Copy Markdown
Member

Batch size was derived from the first row's column count, but Drizzle emits one bound parameter per populated column per row. When later rows were wider than the first, a batch could exceed the bound parameter limit (e.g. D1's "too many SQL variables"). Size batches by the widest row instead.

Fixes #16964

Batch size was derived from the first row's column count, but Drizzle
emits one bound parameter per populated column per row. When later rows
were wider than the first, a batch could exceed the bound parameter
limit (e.g. D1's "too many SQL variables"). Size batches by the widest
row instead.
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

📦 esbuild Bundle Analysis for payload

This analysis was generated by esbuild-bundle-analyzer. 🤖
This PR introduced no changes to the esbuild bundle! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sqlite batch-insert under-counts params/row

1 participant