mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
3abbad048e
A restore commits its transaction and then rebuilds the chart tiers. A worker that stopped during that rebuild left the job running with a stale heartbeat, and the boot sweep and the admission check treated it like any interrupted job: the sweep queued it again, so the second run deleted and re-wrote the account and lost whatever was written in between, and a second interruption closed it with "rolled back, nothing was changed", which was false. The job now records `committedAt` (added to migration 0347, which has not shipped) and awaits that write before the rebuild starts. The sweep and the admission check close a committed job as `failed_after_commit`, never queue it again, and evict the account's caches. The rebuild itself is left to the nightly and boot passes that already rebuild missing tiers. The module comment now says what an interrupted restore does (restarted once, then failed) and what happens to other writes while a restore runs: new rows are written at once, updates to rows the restore already deleted wait on their lock until it commits or rolls back.
prisma/
The database layer. HealthLog runs PostgreSQL 16 via Prisma 7. This directory holds the single schema file and the forward-only migration history; the generated client is emitted elsewhere.
Contents
schema.prisma— 61 models, one file.cuid()primary keys,snake_casecolumns via@map(...), encrypted columns mostly suffixed*Encrypted(search the file; there are 24 encrypted column references). Thegenerator clientblock emits to../src/generated/prisma(imported as@/generated/prisma).migrations/— numbered, forward-only SQL migrations (0001_…upward).migration_lock.tomlpins the provider topostgresql.
Migration workflow
# author a migration from a schema edit
pnpm dlx prisma migrate dev --name <short_snake_case_name>
# regenerate the client after any schema change
pnpm dlx prisma generate
Number a new migration with the next free prefix. The production entrypoint runs prisma migrate deploy on boot, so every migration must apply cleanly forward — there is no down-migration path. Always include the migration file in the same change as the schema edit.
Conventions
- Encryption is fail-closed:
*Encryptedcolumns are written through@/lib/crypto(AES-256-GCM, versioned key ids); never store plaintext in an encrypted column. Key rotation isscripts/rotate-encryption-key.ts+docs/ops/encryption-key-rotation.md. - The generated client under
src/generated/prismais build output — do not edit it. - Schema-touching changes that affect the API surface must regenerate
docs/api/openapi.yaml(see../CLAUDE.md).
Related: ../src/lib/README.md (db.ts, rollups/), ../docs/ops/ (migrations + backup runbooks).