> without any issue It's easier than you think to corrupt SQLite if you access from multiple threads and especially from multiple processes (yup, I've done thi

> without any issue It's easier than you think to corrupt SQLite if you access from multiple threads and especially from multiple processes (yup, I've done this before). Also, there are no concurrent transactions in SQLite. The entire db file gets locked (using POSIX locking, which is known to be broken [0]). Better to queue/batch transactions on a single connection. If your web server consists of multiple processes, then this requires a separate daemon. [0]: http://0pointer.de/blog/projects/locking.html http://0pointer.de/blog/projects/locking.html