Kyle Isom 20d8d8d4b4 Set MaxOpenConns(1) to eliminate SQLite SQLITE_BUSY errors ...

Go's database/sql opens multiple connections by default, but SQLite
only supports one concurrent writer. Under concurrent load (e.g.
parallel blob uploads to MCR), multiple connections compete for the
write lock and exceed busy_timeout, causing transient 500 errors.

With WAL mode, a single connection still allows concurrent reads
from other processes. Go serializes access through the connection
pool, eliminating busy errors entirely.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-25 23:28:46 -07:00

..

db_test.go

Initial commit: project setup and db package

2026-03-25 14:17:17 -07:00

db.go

Set MaxOpenConns(1) to eliminate SQLite SQLITE_BUSY errors

2026-03-25 23:28:46 -07:00