A zero-dependency, ultra-lightweight database time machine for SQLite
thunderbong
34 points
4 comments
August 09, 2026
Related Discussions
Found 5 related stories in 66.8ms across 4,128 title embeddings via pgvector HNSW
- Choose DuckDB rather than SQLite rubenvanwyk · 85 pts · July 29, 2026 · 53% similar
- Learning a few things about running SQLite surprisetalk · 206 pts · July 17, 2026 · 53% similar
- Show HN: SirixDB 1.0 Beta – Git-Like Versioning, Diffs, Time-Travel Queries lichtenberger · 12 pts · July 15, 2026 · 49% similar
- SpacetimeDB: A Short Technical Review hurrrr · 78 pts · August 20, 2026 · 48% similar
- Tailscale Traces Database Corruption to 16y/o SQLite WAL-Reset Bug ropbear · 930 pts · August 12, 2026 · 48% similar
Discussion Highlights (2 comments)
simonw
https://github.com/nsrht/time-travel-sqlite-debugger/blob/ma... works by checking the mtime on the database file (and -wal file) once per second and creating a backups/unixtime_database.sqlite file if anything has changed, then keeps the last 50 copies. So OK for smaller database files but not great if you're pushing into a GB+ of data. I'm not convinced by the way it copies the files - I think using a "vacuum into" backup would be safer then file copies. Litestream offers point-in-time recovery for SQLite by backing up chunks of WAL directly, which I expect is a lot more efficient than this mechanism.
corysama
I can imagine abusing this to implement undo-redo for a game editor. Take snapshots. Record actions. Implement undo as: role back to a snapshot and re-run actions from the snapshot to the desired state.