ContextArticle

Users should back up their existing logs.db before upgrading to the RC, even though the schema change only adds new tables.

Recommends precautionary backup before applying the RC despite backward compatibility. ✦ AI generated

Release author · Simon Willison's Weblog · 2026-07-30 · original ↗

Since it involves a significant schema change - new tables only, and old data should not be affected at all - it's worth running a backup of your existing logs.db before upgrading to the RC

Read full article ↗excerpt · fair-use quotation

✳ LLM

Related moments

PredictionAudio · 33:40 · 2m

A post-quantum Bitcoin upgrade needs to be agreed upon in 2026 because consensus takes at least a year and the migration itself takes 6-12 months, putting us on the leading edge of the risk window starting in 2027.

Charles Edwards · We Study Billionaires

Mechanism◆Article · 33 words

Content-addressable hash IDs for stored messages enable deduplication in the database and allow LLM to represent trees of messages for forked conversations.

Release author · Simon Willison's Weblog

Mechanism◆Article · 22 words

In sqlite-utils 4.2, transform() preserves a much larger array of edge-case schema definitions, including check constraints, unique constraints, and even comments describing the columns.

Simon Willison · Simon Willison's Weblog