v149 · Storage · IndexedDB
Error Recovery
The SQLite migration was driven partly by reliability: the old LevelDB backend had bug reports for corruption after aborted transactions and torn writes. These tests verify that aborts, constraint errors, and version-change events all leave the database in a clean, consistent state.
what the tests check
SQLite's write-ahead log (WAL) mode means that a transaction abort at any point rolls back atomically — no partial writes survive. The tests here exercise abort scenarios that were historically problematic with the LevelDB/flat-file backend: explicit abort, error-triggered abort, constraint violations, and concurrent-write isolation.
see also
- Concurrent Reads Test — parallel read consistency
- Transaction Durability — atomicity and isolation
- Bulk Write Stress Test — throughput benchmark
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗