In-memory database access fails with multiple goroutines about go-sqlite3 HOT 3 CLOSED

Of course as soon as I posted this I found the FAQ entries that somehow I had missed. To recap for anyone else stumbling around, without the ?cache=shared flag any additional database connections that are used internally from a connection pool will see different databases, and therefore can run into the "no such table" problem.

But enabling the shared cache flag will now potentially cause a "database table is locked" error if multiple goroutines attempt to access the table. So some kind of application-level locking is required to handle that.

from go-sqlite3.

@rob94110 The modern recommendation is to use the memdb vfs (i.e., file:/foobar?vfs=memdb), not shared cache. Note that the leading slash is required.

from go-sqlite3.

Thank you! I can't find any definitive documentation for this feature for some reason.

from go-sqlite3.