3 ms·
> Multithreaded use is not supported To be more precise, it's perfectly legal to use SQLite from multiple threads or processes at the same time. It will use it
by teraflop 12y ago
> Multithreaded use is not supported
To be more precise, it's perfectly legal to use SQLite from multiple threads or processes at the same time. It will use its own mutexes and OS file-locking operations to ensure that at any given time, a database is being accessed by either a single writer, or an arbitrary number of readers.
In my opinion, the bigger issue is that clients can only safely access a SQLite database if it exists on a local filesystem. As soon as you decide you want to run multiple web servers, you're in trouble.
- StavrosK 12y agoSorry, yes, that's what I meant. I use it for a mostly-read-only Web app, but wasn't sure if it's a disaster waiting to happen. Good to know it's a viable alternative to postgres in multithreaded or multiprocess scenarios.
- reitanqild 12y agoI ran it as a replacement for MySQL for 3 years, light usage php web app, around 100 - 200 users I guess. It saved me quite some hassle and reduced the attack surface compared to MySQL. FWIW I never bumped into speed issues. My biggest issue against it is that it would let me alter columns directly which effectively sabotaged my use of alembic when I started using Python/flask.
- StavrosK 12y agoHuh, that sounds like it worked very well. Plus, the reduced overhead of backups etc is definitely worth it for small apps.