Keep Today and Later reads available during planning writes #700

2026-08-13T02:22:43Z

timmy commented

2026-08-13 02:22:43 +00:00

Closes #699

What changed

migrate Today and Later SQLite schemas once per database version instead of on every connection
keep ordinary connections free of WAL setup, DDL, migration backfills, and commits
prove initialized reads remain available during an independent planning write

Verification

RED: both new lock-contention tests failed with sqlite3.OperationalError: database is locked
focused: 21 passed
full suite: 1367 passed in 73.77s
contention probe: 100/100 reads succeeded for both stores while a writer held BEGIN IMMEDIATE

Closes #699 ## What changed - migrate Today and Later SQLite schemas once per database version instead of on every connection - keep ordinary connections free of WAL setup, DDL, migration backfills, and commits - prove initialized reads remain available during an independent planning write ## Verification - RED: both new lock-contention tests failed with `sqlite3.OperationalError: database is locked` - focused: `21 passed` - full suite: `1367 passed in 73.77s` - contention probe: 100/100 reads succeeded for both stores while a writer held `BEGIN IMMEDIATE`

timmy added 1 commit 2026-08-13 02:22:44 +00:00

perf: keep planning reads available during writes (Closes #699 )

CI / lint (pull_request) Successful in 1m28s

Details

CI / build-release (pull_request) Successful in 5s

Details

CI / release-candidate (pull_request) Has been skipped

Details

1de6d73e75

timmy merged commit 71d06347fd into main

2026-08-13 02:24:46 +00:00

timmy referenced this issue from a commit

2026-08-13 02:24:47 +00:00

Merge pull request 'Keep Today and Later reads available during planning writes' (#700)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#700