Phase 09 · Lesson 02

Install and Lock Prisma 7 9 1

≈ 2 min core reading · 441 source/companion words

Learning contract

What you should be able to do after this

Explain Install and Lock Prisma 7 9 1 without relying on framework buzzwords.
Connect the lesson to the phase outcome: Integrate Prisma 7.9.1 as a repeatable persistence layer with schema, generated client, adapter/configuration, migrations, and NestJS lifecycle.
Reproduce the relevant behavior and verify it with evidence.
Diagnose at least one representative failure instead of guessing.

Figure 9.2 — TaskFlow boundary map

schema.prisma

migration files

database schema

generated Prisma Client

PrismaService

feature service

This lesson belongs to Phase 09. Keep the full request/data path visible even when today's code changes only one box.

Instructor workflow: predict first → implement the smallest slice → run it → inspect evidence → break one assumption → diagnose → explain it back. Do not copy the whole code block before understanding the first failing boundary.

PHASE 09 / BOOK 02

Install & Lock Prisma 7.9.1 Exact dependencies, local CLI and reproducible tooling

NestJS

PrismaService

Prisma Client

PrismaPg driver adapter

Supabase PostgreSQL

Figure - The database access stack introduced in Phase 09

Course rule: Prisma CLI, @prisma/client and @prisma/adapter-pg are locked to 7.9.1. Newer Prisma releases are not substituted halfway through the course.

1. Work From the API Package All Prisma database tooling stays inside apps/api for now. We do not create packages/database merely because the repository has a packages folder. The backend is currently the only owner of database access. PowerShell - verify location

Get-Location # Expected path ends with: taskflow\apps\api

2. Install Exact Versions PowerShell - install the locked Prisma stack

Terminal

# From: taskflow\apps\api
pnpm add -D prisma@7.9.1 @types/pg
pnpm add @prisma/client@7.9.1 @prisma/adapter-pg@7.9.1 pg dotenv @nestjs/config

The CLI is a development dependency. The generated client runtime, adapter and pg driver are runtime dependencies because the NestJS API uses them while running.

Package responsibilities Package Type Why it exists

prisma@7.9.1 dev CLI: init, validate, generate, migrate, studio

Code

@prisma/client@7.9.1                runtime           Runtime package used by generated Prisma Client

Code

@prisma/adapter-pg@7.9.1            runtime           Prisma 7 PostgreSQL driver adapter

pg runtime Underlying PostgreSQL driver

dotenv runtime/tooling Loads .env for Prisma config/scripts

Code

@nestjs/config                      runtime           Loads trusted backend configuration into Nest DI

Code

@types/pg                           dev               TypeScript declarations for pg when needed

3. Verify the Local CLI PowerShell - use the project-local CLI

# From: taskflow\apps\api pnpm exec prisma version

Do not rely on a globally installed prisma executable. pnpm exec resolves the version declared by this project, which is exactly the reproducibility we want in a long course.

EXPECTED The Prisma CLI line and @prisma/client line should report 7.9.1. Stop if one package reports a different version.

4. pnpm Build Approval If pnpm reports ignored dependency build scripts, treat that as a supply-chain security decision rather than a broken install. PowerShell - only if pnpm tells you builds were ignored

Terminal

pnpm approve-builds

Approve only packages that are actually required by this project. Do not globally disable script protection.

5. Why Exact Versions Matter • Generated Client code is tied to the Prisma generation toolchain.

• Breaking CLI/config behavior can change across major releases.

• A course that silently upgrades becomes impossible to debug because two learners can follow the same page and get different generated output.

• Locking versions turns documentation into a reproducible engineering artifact.

Checkpoint Verify all three course-critical packages

Terminal

pnpm exec prisma version
pnpm list prisma @prisma/client @prisma/adapter-pg

Executable lesson studio · prisma

Now turn the explanation into engineering skill.

Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.

By the end, you should be able to

Explain Install and Lock Prisma 7 9 1 in terms of concrete inputs, ownership, outputs, and evidence.
Implement or reproduce the smallest TaskFlow slice that demonstrates this prisma concept.
Diagnose one representative prisma failure using observable evidence instead of trial-and-error.

Figure 9.2B — Mental model

domain intent

Prisma Client

generated SQL

PostgreSQL

mapped result

Read left-to-right while implementing. When debugging, walk right-to-left until the first observed fact differs from your prediction.

Code-along sequence

One coherent change at a time

01
Restate the goal of “Install and Lock Prisma 7 9 1” as one observable behavior. Write the success signal before touching code.
02
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. Mark the one boundary this lesson changes.
03
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
04
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
05
Connect the slice to TaskFlow’s phase artifact: Prisma schema + migration history + generated client + NestJS PrismaService connected to TaskFlow PostgreSQL.. Verify behavior from the outside as a user or API client would.
06
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
07
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.

tsKeep the generated client visible in the mental model

const tasks = await prisma.task.findMany({
  where: { workspaceId },
  orderBy: [{ createdAt: "desc" }, { id: "desc" }],
  take: 20,
});

Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.

Verification

Prove the happy path

Run the narrowest relevant command or request and require a clean exit/status.
Inspect the boundary-specific evidence: terminal output, Network panel, database row/query plan, test report, container health, or deployment logs.
Repeat the behavior once after the change so a one-off cached or stale result cannot masquerade as success.

Break it on purpose

Build debugging memory

Editing generated client code
Change one assumption in the prisma example—identity, input, configuration, ordering, connectivity, or state—and predict the exact symptom before running it.

SymptomInvestigation path

P1001 / connection failure

Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.

Migration surprises

Read the generated SQL before applying it and compare the change against existing production-shaped data.

Closed-reference challenge

Can you transfer the idea?

Without copying the final source, create a second small scenario that applies “Install and Lock Prisma 7 9 1” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.

Explain-back

Answer these without reopening the solution

What problem does Install and Lock Prisma 7 9 1 solve in TaskFlow, and what would be observably wrong without it?
Which part of the prisma boundary owns the decision, and which neighboring layer must not own it?
What evidence proves the happy path instead of merely suggesting it worked?
Name one realistic failure or abuse case and the first place you would inspect.
If requirements doubled tomorrow, which part of this design should stay stable and which part is allowed to change?

Lesson studio

Turn the reading into skill

Do it

Initialize Prisma with the intended generated-client output and PostgreSQL configuration.

Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.

Break it safely

Editing generated client code

Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.

Explain it back

Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?

If your explanation is vague, repeat the boundary trace before moving on.

Exit ticket

Before marking complete

Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.

← Prisma Mental Model and Architecture Prisma Init and File Anatomy →