Skip to content(if available)orjump to list(if available)

An adventure in writing compatible systems

An adventure in writing compatible systems

3 comments

·August 29, 2025
Visit

ozgrakkurt

Curious if having the automated tests do db operations on a persistent db would catch this.

It would do inserts/deletes/updates/create_table/alter_column etc. randomly for a long time, continue even if an operation fails unless there is a crash. This way the db could grow without bound and queries can get very slow

swiftcoder

It only catches it if you re-load the DB into sqlite after every write by turso. At which point you'd flag pretty quickly that it was the next write after 1 GB that messed things up

ozgrakkurt

Could also make switching an operation. So it randomly switches between implementations and keeps using it until the next switch. And can keep running two instances so it is always kind of cross checking