mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
72c259d85c
A resumable collection counted the pages it had written across every backfill attempt and stopped at its ceiling (10,000 for heart rate). A watch that records heart rate every few seconds reaches that count two to three years back, and since it never reset, every later slice stopped at the same place, failed as stuck, and the backfill was never stamped complete. A walk is now stopped only when it stops moving: 20 pages in a row that reach no further back than the pages before them end it. A history backfill reads back at most GOOGLE_HEALTH_BACKFILL_HORIZON_YEARS (20 when unset). A data type that ends either way counts as finished, and where and why it ended is kept in backfillProgress past the completion stamp. An oldest-first list is read whole, as before. The slice chain's ceiling is derived from sixty days of back-to-back slices instead of the old page count. An account left at the old ceiling continues from its edge with the next slice. Refs #1220
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).