SQLite has a robust locking mechanism. For a write, a connection has to acquire an exclusive lock on the DB. This can significantly affect the performance in multi-writer situations. Any failure in the locking mechanism would be a high priority bug.
In reply to Re^3: DBD::SQLite "file is encrypted or is not a database" in running application
by Marshall
in thread [SOLVED]: DBD::SQLite "file is encrypted or is not a database" in running application
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |