clawbot fc080147af 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 run on it one at a time 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 and that requests wait while
eviction runs one of its queries.

Model: opus-5-5

2026-10-08 02:00:17 +00:00

..

concurrent_writes_internal_test.go

Queue SQLite writes on one connection so none fails as locked (closes #223)

2026-10-08 02:00:17 +00:00

database_internal_test.go

next -> main (1.0.0 milestone) (#105)

2026-09-21 09:31:54 +02:00

database.go

Queue SQLite writes on one connection so none fails as locked (closes #223)

2026-10-08 02:00:17 +00:00

migrations_internal_test.go

Move migrations to internal/db/migrations (closes #96)

2026-09-29 07:42:05 +02:00