Hacker News Reader

I don't know exactly what you mean, but sqlite probably supports your use case.

sqlite's defaults balance performance, flexibility, and backwards compatibility. They don't work for every case, but there is almost always a lever to pull.

The downside is you have to learn them. The docs are really excellent, though.

What is a persistent data memory user?

true, concurrency, let alone parallelism, never worked for me when i tried it. never used in anywhere. sounds good in theory but it is unusable for most real world cases. there are endless key-value databases suitable for 90% of what sqlite does. and if you truly need multiple indexes per table and joins, just use a proper rdbms and stop playing around.

> sounds good in theory but it is unusable for most real world cases.

Are you sure about that? You are talking about the single most widely deployed piece of software ever.

Did you use WAL mode and BEGIN IMMEDIATE TRANSACTION?

Why?

no transactions on data description layer?

CREATE TABLE etc in SQLite are fully transactional, as are updates to PRAGMA user_version which you can use to store a logical schema version number. I built Notion’s SQLite migration system for client devices on those primitives.