3 ms·
Sqlite has really 1 big problem in my mind. 1 thread at a time. If you try to have 2 threads throwing stuff at it. _sqlite.OperationalError: database is locke
by incomingpain 4y ago
Sqlite has really 1 big problem in my mind.
1 thread at a time. If you try to have 2 threads throwing stuff at it.
_sqlite.OperationalError: database is locked
This is what makes it a toy database. Mind you, sqlite will handle most projects, but those are also toy projects.
- adamckay 4y agoIs this not resolved with WAL mode? You can't have concurrent writes, but they can go into a "queue" so as long as you have fast writes and suitable timeouts they'll still be committed. So whilst they're not technically concurrent, as far as a human using your app will be concerned it will feel concurrent because they were able to write at the same time as someone else, just at an imperceivable fraction of a second slower.
- incomingpain 4y agoThere are a few options that make it possible do get around db locks but none of them worked for me.