4 ms·
> but this where you get all of your performance caveats. You mean the one where it locks on write? It’s totally fine, if you wrote any cross process code your
by liontwist 2y ago
> but this where you get all of your performance caveats.
You mean the one where it locks on write? It’s totally fine, if you wrote any cross process code yourself it’s probably going to do similar locking.
- immibis 2y agoYeah, but you're locking the whole file and if you try to open it while it's locked, sleep-polling for it to be unlocked. It's safe, but it's a minimum viable product - as they say, sqlite is a replacement for fopen, not for a fully featured database. Client/server systems have better locking.
- liontwist 2y agoI mostly agree. If you need an RDMS get a real one that has all the features and granular locking. The only point I’m disagreeing about is the blanket statement “your SQLite website won’t work if it has concurrent writers”. It will.