Track project · 10

Add Prisma without Losing the Database Mental Model

Map the known PostgreSQL design into Prisma, inspect generated SQL, and build persistent task operations safely.

Build plan

Work through it one observable step at a time

01
Model the existing tables in `schema.prisma`.
02
Generate the client and inspect where generated types come from.
03
Create PrismaService in NestJS and prove connection startup/shutdown behavior.
04
Create a development migration and open the generated SQL before applying it.
05
Seed realistic TaskFlow data.
06
Implement one relation query and inspect its SQL/query count.
07
Use a transaction for one multi-write operation.
08
Simulate a dangerous NOT NULL change and rewrite it as expand → backfill → verify → contract.
09
Document the production migration sequence separately from local `migrate dev`.

Evidence

Do not rely on “it seems to work”

Evidence to collect

A clean Git diff or file-tree changeCommands used and their exit/resultBrowser, HTTP, database, test, container, or CI evidence that proves the behaviorOne deliberate failure, the evidence you used, and the root-cause fixA short explanation of why the final responsibility lives in the chosen layer

Project exit ticket

Close the project only when these are true

Completion

I can demonstrate every deliverable.I can reproduce one key part without the walkthrough.I can explain one trade-off I deliberately chose.I can show one failure that my tests, constraints, or runbook now protects against.