>> Every 30 seconds, stop writing, make a copy of the old database That sounds so simple that i almost glossed over it. But then the alarm bells started ringin

>> Every 30 seconds, stop writing, make a copy of the old database That sounds so simple that i almost glossed over it. But then the alarm bells started ringing. If you don’t need to collaborate with other people, this kind of hacking is mostly fine (and even where its not fine, you can always upgrade to using filesystem snapshots to reduce copy burden when that becomes an issue and use the sqlite clone features to reduce global lock contention when you grow into that hurdle etc etc) but if you need to collaborate with others, the hacky approaches always lead to tears. And the tears arrive when you’re busy with something else.