mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
bb1e01e456
Migration 0276 reverses the rows that reached EXPIRED only through the post-opening clock on a container that never had one. It moves a row back to IN_USE when an opening date is recorded and ACTIVE when none is, and sets `expires_at` from the printed expiry — which for these rows is usually nothing at all, because they recorded none. The predicate is exact rather than approximate: nothing but the printed expiry and the in-use clock can write EXPIRED, so a clock-less container whose printed expiry is absent or still ahead can only have got there through the clock. Pens and ampoules keep their EXPIRED, so does anything whose printed date genuinely lapsed, and so does a drained container. No date is invented and no printed expiry is fabricated. The integration test seeds the before-state, applies the migration SQL from disk, and asserts both what moves and what stays — the testcontainer starts empty, so the migration running at boot proves nothing on its own.
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).