geniusrun

Files

Christophe Vila 46ad8a7e08 store: test that pre-existing FK-referencing rows survive the 0023-0025 rebuild

Every existing migration test opens a brand-new DB via store.Open, which
runs migrations 0001-0025 in one uninterrupted pass over an empty
database -- so migrations 0023/0024/0025's table-rebuild (create-new/copy/
drop-old/rename-into-place) never had any real pre-existing rows to carry
across, and no test proved that a genuinely in-use single-tenant install
(real workout_kinds, real synced activities, kind_assignments referencing
workout_kinds by FK) upgrades safely.

TestRebuildMigrationsPreserveForeignKeyReferences manually applies
migrations up to (but not including) the three rebuilds, inserts rows
simulating that pre-existing install, applies the rebuilds, then verifies
the kind_assignments row still resolves to the correct workout_kinds row
by name, and that FK enforcement is genuinely back on afterward (a bogus
workout_kind_id is rejected).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-25 12:25:01 +02:00

migrations

store: add users table and user_id scoping to migrations

2026-07-25 10:20:59 +02:00

activities.go

Rename smartrun to geniusrun throughout the codebase

2026-07-24 21:08:07 +02:00

assignments.go

Replace per-kind reclassify with a single global reclassify that respects manual and Race locks

2026-07-19 11:11:50 +02:00

db.go

store: fix PRAGMA foreign_keys scoping for table-rebuild migrations