This is really not true in WAL mode with synchronous NORMAL, this was only true with the default journal mode and a lot of people are misusing sqlite because of

This is really not true in WAL mode with synchronous NORMAL, this was only true with the default journal mode and a lot of people are misusing sqlite because of that. You still have one writer at a time but you wont get the SQLITE_BUSY error. You can check the documentation [1], only some rare edge cases return this error in WAL. We abuse our sqlite and I never saw it happen with a WAL db. [1] https://www.sqlite.org/wal.html#sometimes_queries_return_sqlite_busy_in_wal_mode https://www.sqlite.org/wal.html#sometimes_queries_return_sql...