Skip to content

fix(db): auto-migrate prebuild-guarded indexes on small databases #8802

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TheSentinel454 merged 6 commits into from
Nov 5, 2026
Merged

fix(db): auto-migrate prebuild-guarded indexes on small databases #8802

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
23a5b1a
fix(db): auto-migrate artifact sync indexes on small databases
TheSentinel454 Oct 30, 2026
ea51ce2
fix(db): build each inline migration index in its own transaction
TheSentinel454 Oct 30, 2026
64cce23
fix(db): build 0081's index at startup and forbid populated-table ref…
TheSentinel454 Nov 4, 2026
6c3768b
docs(db): limit operator prebuilds to out-of-band migration
TheSentinel454 Nov 4, 2026
5ca55f9
test(db): boot verified-profile databases through 0081 separately
TheSentinel454 Nov 4, 2026
a481b5b
docs(db): reconcile Rule 3 with inline index builds
TheSentinel454 Nov 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,9 @@ Before planning or reviewing a non-trivial change:
4. For any change to `migrations/`, `schema/`, or schema-dependent `buzz-db`
queries, read [docs/database.md](docs/database.md): no new triggers,
functions, or foreign keys; no data backfills in migrations; update every
schema location; and keep every migration compatible with the relay that
is currently deployed.
schema location; keep every migration compatible with the relay that
is currently deployed; and never make a migration refuse a populated
table.
5. Check that the proposed design advances, or at least does not contradict,
that product intent. Call out any intentional tension explicitly.

Expand Down
Loading
Loading