go-sqlite3: `database is locked` regression

I had the same issue after updating to current version. I found the solution that works for me so maybe it will help in your case.

I had sqlite file in WAL journal mode. But new driver couldn’t connect to it, until i changed my connection strings in all my projects, so it contains “&_journal_mode=WAL” in dsn.

Setting “?cache=shared&mode=ro&_busy_timeout=9999999” alone, and adding db.SetMaxOpenConns(1) was insufficient.

There is no issue using SQLite concurrently, provided that you understand certain interactions between database/sql and SQLite itself.

One of the ways that people get the “database is locked” errors is they attempt to modify the database in the middle of a rows.Next() loop. When you do that, database/sql tries to use a second database connection, since the first one is still “in use”. But under journal mode (the default), a second database connection cannot modify the database while the first connection has a read lock. So the second connection hits its busy timeout and returns that error. To resolve this, you need to make both the reads and writes part of the same transaction.

Another way that error can happen is if you attempt to read and then write within a single transaction (in either WAL mode or journal mode). If another connection modifies the database between the read and the write, you will get that error because SQLite can no longer guarantee the consistency of the data your transaction has been working with. To resolve this, you need to use IMMEDIATE transactions.

You should never use shared cache mode, as doing so just leads to further issues.