Upgrading rusqlite 0.39 to 0.40
Breaking0.39.0 → 0.40.2Breaking6Security1Platform1New4Changed6Fixed1Other5
BreakingUpgrade verdict
6 breaking changes and a platform requirement change and a security fix.
In plain terms
- Code that used the old macros to define virtual tables must switch to the new constructor functions.
- Fixes VTab::best_index, changing its behavior for callers.
- Fixes VTab::connect and create, changing their behavior for callers.
- Allows opting out of using sqlite-wasm-rs on wasm32-unknown-unknown.
Must act Top 5 of 8 that need code or config changes
What you must change
Breaking6
Replaces VTab macros with constructors.
VTabFixes VTab::best_index, changing its behavior for callers.
VTab::best_indexFixes VTab::connect and create, changing their behavior for callers.
VTab::connectAllows opting out of using sqlite-wasm-rs on wasm32-unknown-unknown.
sqlite-wasm-rsFixes VTab::connect, changing its behavior for callers.
VTab::connectFixes vtab::dequote, changing its behavior for callers.
vtab::dequoteSecurity1
Fixes SQL injection when the SAVEPOINT name is tainted.
SAVEPOINTPlatform1
Lowers the minimum supported Rust version (MSRV) to 1.88.0.