Configure SQLite foreign keys, WAL mode, and busy timeout #17

New issue

Closed

opened 2026-09-04 23:26:52 +02:00 by arne · 0 comments

arne commented

2026-09-04 23:26:52 +02:00

Owner

Apply and verify the SQLite connection settings required for correctness and useful concurrent HTTP access.

Acceptance criteria:

Every database connection enforces foreign keys; configuration does not rely on a one-time pragma applied to only one pooled connection.
WAL journaling is enabled and verified at startup.
A documented non-zero busy timeout is applied consistently to connections.
Startup fails with contextual errors when required settings cannot be applied or verified.
Tests assert foreign-key enforcement, journal mode, busy timeout, and behavior across more than one acquired connection where applicable.
make check passes.

Dependencies:

Depends on #16.

Apply and verify the SQLite connection settings required for correctness and useful concurrent HTTP access. Acceptance criteria: - Every database connection enforces foreign keys; configuration does not rely on a one-time pragma applied to only one pooled connection. - WAL journaling is enabled and verified at startup. - A documented non-zero busy timeout is applied consistently to connections. - Startup fails with contextual errors when required settings cannot be applied or verified. - Tests assert foreign-key enforcement, journal mode, busy timeout, and behavior across more than one acquired connection where applicable. - `make check` passes. Dependencies: - Depends on #16.

arne added this to the Milestone 1: runtime foundation milestone

2026-09-04 23:26:52 +02:00

arne referenced this issue

2026-09-04 23:27:01 +02:00

Add embedded SQLite migrations and migration tests #18

arne referenced this issue

2026-09-04 23:27:09 +02:00

Add database integration-test support #19

arne referenced this issue from a pull request that will close it,

2026-09-05 08:30:22 +02:00

Configure SQLite runtime settings #27

arne referenced this issue from a commit