Files
pixa/internal
clawbot 9e64435e66
check / check (push) Waiting to run
Queue SQLite writes on one connection so none fails as locked (closes #223)
internal/database now opens the database with one connection. pixa's
own reads and writes wait for it in turn instead of competing for
SQLite's lock, where a write that kept losing could wait past the
five-second busy timeout and fail with "database is locked". The busy
timeout stays, for another program writing to the same file.

With one connection, a query run while rows or a transaction are still
open would wait forever. No code in internal/database or
internal/imgcache does that; the comment on DB() tells callers.
README.md says pixa uses one connection.

Model: opus-5-5
2026-10-08 00:33:04 +00:00
..