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.
⚡ Bolt: [performance improvement] Pre-allocate String and use write! for D1 SQL generation #199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
⚡ Bolt: [performance improvement] Pre-allocate String and use write! for D1 SQL generation #199
Changes from all commits
5ece998File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These builders currently tolerate missing key parts by skipping absent entries (
key.0.get(idx)), which can lead to partial key predicates (or even none) and therefore wrong-row updates/inserts or overly-broad deletes for composite keys. Since key/value arrays are positional, consider validating thatkey.0.len()matcheskey_fields_schema.len()(and similarly for values) and returning aRecocoErrorinstead of silently generating a different statement.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
build_delete_stmtstarts the SQL with... WHEREeven if no key parts are appended (e.g., empty key schema or a shorter-than-expectedKeyValue). That yields a syntactically invalid statement and obscures the real problem. Consider early-returning an error when zero predicates are emitted (and/or when the key length doesn't match the schema) before returning the SQL.Uh oh!
There was an error while loading. Please reload this page.