Part 06 of the notebook
DATABASEDatabase
Supabase, Postgres and Prisma errors, reproduced on a real local stack: the error code, the cause, the fix. Every database error here was reproduced on a real local stack, with the exact client, server and Postgres versions, before it was written up.
press / and paste the error your client printed.
By topic:Prisma (3)
- No.052
Prisma P1001: Can't reach database server at localhost:5432
P1001 prints the same words for five different problems, Docker and Supabase included. Each one reproduced, plus a one-line check that tells them apart.
> Error: P1001: Can't reach database server at `localhost:5432`
DATABASE5 min - No.049
Fix: @prisma/client did not initialize yet (Prisma 6 and 7)
The error says run prisma generate. Why it keeps coming back on Windows, npm 12 and CI, reproduced, plus the errors Prisma 7 throws instead.
> D:\project\node_modules\.prisma\client\default.js:43
DATABASE4 min - No.048
prisma generate not working: "No command registered" (Prisma 8)
npm now installs a Prisma 8 release candidate as prisma@latest. It has no generate, migrate dev or db push. Reproduced, with the fix for Docker and CI.
> {"kind":"result","envelope":{"ok":false,"commandId":"","error":{"code":"CLI.UNKNOWN_COMMAND","severity":"error","summary":"No command registered for `generate`","nextActions":[{"kind":"run-command","label":"List every command","command":"prisma --help"}]}}}
DATABASE4 min - No.047
Supabase error 42501: new row violates row-level security policy
Supabase's 42501 has two messages and seven causes. Each reproduced on a local stack, plus the October 30 change that breaks new tables.
> {
DATABASE6 min
Post card · Newsletter
Get the next fix in your inbox.
One short email when a new entry is published. No spam, never shared, and you can leave any time.
— Nilay