Compile sqlite with SQLITE_ENABLE_UPDATE_DELETE_LIMIT #932
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.
I have a project that runs sqlite queries in the form
DELETE FROM X ... LIMIT Y. When I was using a Debian-provided Python, these queries worked properly. But when I used a Python installed byuv(via this project), the queries failed with a syntax error.I tracked it down to a difference in the compile-time options for sqlite. Debian compiles sqlite3 with
-DSQLITE_ENABLE_UPDATE_DELETE_LIMIT=1but this project dooes not.Are you all open to adding this compilation flag?
This option enables an optional ORDER BY and LIMIT clause on UPDATE and DELETE statements: https://sqlite.org/compile.html#enable_update_delete_limit
It is enabled by default in the Debian sqlite3 package: https://sources.debian.org/src/sqlite3/3.46.1-8/debian/rules#L51