4 ms·
idk, the author themselves don't recommend it: >If many threads and/or processes need to write the database at the same instant (and they cannot queue up and t
by endisneigh 4y ago
idk, the author themselves don't recommend it:
>If many threads and/or processes need to write the database at the same instant (and they cannot queue up and take turns) then it is best to select a database engine that supports that capability, which always means a client/server database engine.
https://www.sqlite.org/whentouse.html https://www.sqlite.org/whentouse.html
- simonw 4y agoThat reads to me like a somewhat-sarcastic way to make fun of people who think SQLite can't handle their write load. Not a lot of applications have many processes that need to write at the same instant in time and cannot be put in a queue instead.
- antifa 4y agoWhy build a queue before you really need it when you can just use postgres?