Skip to content
Library

Prisma

Official site

Playbooks for Prisma

  1. Fixing PrismaClientInitializationError from a missing or bad connection string

    Covers environment/connection-string configuration specifically: the string never reaching the deploy environment, a name mismatch against what schema.prisma expects, or unescaped special characters. Does not cover P1001 (a valid-looking connection string that simply can't reach the server over the network) — that's a separate playbook — and does not cover query engine binary/platform mismatches beyond flagging them as a possibility.

    Unverifiedno reproductions yetWhy this confidence?

  2. Diagnosing Prisma P1001 (can't reach database server)

    Covers confirming basic network reachability to the named host:port and the usual reasons it's blocked. Does not cover a missing or malformed connection string (see the PrismaClientInitializationError playbook) — by the time you have a specific host:port in the error, the string was parsed successfully.

    Unverifiedno reproductions yetWhy this confidence?

  3. Handling Prisma P2002 unique constraint violations

    Covers recognising that P2002 is Postgres's unique constraint doing its job, correctly, and the two idiomatic ways to handle an expected duplicate. Does not cover tracing where an unexpected duplicate came from (a retry without an idempotency key, a double-fired webhook, a bad backfill) — this playbook only gets you to recognising which situation you're in.

    Unverifiedno reproductions yetWhy this confidence?

Versions