Mechanism◆Article
Table.delete_where() never wraps its DELETE in a transaction, so it fails to commit and leaves the database connection permanently poisoned, causing silent data loss on subsequent operations.
Claude Fable · Simon Willison's Weblog
Fact◆Article
sqlite-utils now follows SQLite's own convention for treating column names as case insensitive, a change that turned out to touch a bunch of different places in the codebase.
To align with SQLite's built-in case-insensitive column naming, sqlite-utils had to modify multiple areas of its code, not just a single localized fix. ✦ AI generated
Simon Willison · Simon Willison's Weblog · 2026-07-06 · original ↗
sqlite-utils also now follows SQLite's convention for case insensitive column names, which turned out to touch a bunch of different places at once.
Read full article ↗excerpt · fair-use quotation
- ·Now follows SQLite's own convention for column names
- ·Column name matching is now case insensitive
- ·Change required touching many parts of codebase
- ·Not a single localized fix, but a broad update
Related moments
Fact◆Article
The biggest new feature in this release is support for introspecting and creating compound foreign keys, and because that involves a subtle breaking change to table.foreign_keys, it had to land before the 4.0 stable release.
Simon Willison · Simon Willison's Weblog
DefinitionArticle
Every write method in sqlite-utils runs inside and commits its own transaction automatically, so changes are saved to disk as soon as the method call finishes, without needing an explicit commit().
Claude Fable · Simon Willison's Weblog