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
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.
sqlite-utils gains support for compound foreign keys, a feature significant enough that its accompanying breaking change to table.foreign_keys had to be included in the 4.0 stable milestone rather than deferred. ✦ AI generated
Simon Willison · Simon Willison's Weblog · 2026-07-06 · original ↗
The biggest new feature is support for introspecting and creating compound foreign keys - a feature that involves a subtle breaking change to table.foreign_keys and hence needed to land for the 4.0 stable release.
Read full article ↗excerpt · fair-use quotation
- ·Biggest new feature: introspecting compound foreign keys
- ·Also adds creating compound foreign keys
- ·Requires a subtle breaking change to table.foreign_keys
- ·Change had to ship before 4.0 stable release
- ·table.foreign_keys behavior changes, not just additive
- ·Breaking changes must land pre-stable, not after
- ·So this feature gated the 4.0 milestone
Related moments
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.
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