> There is absolutely no reason you can't make SQLite go all the way. No reason you can't, but one you to consider if you should. If you're using libraries whi

> There is absolutely no reason you can't make SQLite go all the way. No reason you can't, but one you to consider if you should. If you're using libraries which make assumptions about your database layer, they may not like the sqlite model. Holding the writer mode for too long is something I experienced in write a few projects. For example paperless-ngx will block the web interface while batch importing documents, even though there's really no reason to do that. It's less of an issue if you write all your own code and you explicitly target sqlite. But worth keeping in mind.