Prisma Error Fixes
Prisma error P2021: The table does not exist in the current database
Prisma's client was generated against a schema that includes a model whose table was never actually created in this specific database — usually because migrations haven't been applied to this environment, or you're connected to the wrong database entirely.
Prisma error P2003: Foreign key constraint failed on the field
You're trying to create or update a record that references a foreign key ID which doesn't exist in the related table — for example, creating an Article with a `pillarId` that doesn't match any real Pillar. Verify the referenced ID actually exists before the write, or handle the error to show a clear message.
Prisma error: Drift detected — your database schema is not in sync with your migration history
Someone (or something) changed the database schema directly — outside of Prisma's migration files — so the actual database no longer matches what Prisma's migration history says it should look like. You need to either reconcile the drift manually or reset the dev database if the data is disposable.
Prisma error: Environment variable not found: DATABASE_URL
Prisma can't find `DATABASE_URL` in your environment at the moment it's reading `schema.prisma` — usually because `.env` isn't in the project root, isn't loaded yet, or the variable name doesn't match exactly what's referenced in your `datasource` block.
Error: @prisma/client did not initialize yet. Please run "prisma generate"
Run `npx prisma generate` to regenerate the Prisma Client after changing your schema, after a fresh `npm install`, or after pulling changes from git — the generated client isn't committed to your repo by default.
PrismaClientInitializationError: Can't reach database server
This means Prisma can't establish a connection to your database at all — usually a wrong `DATABASE_URL`, a paused/suspended Neon project, a missing `?sslmode=require`, or a firewall blocking the connection.
Prisma error P2025: An operation failed because it depends on one or more records that were required but not found
P2025 fires when you `update`, `delete`, or `connect` a record by ID that doesn't exist in the database. Check existence first with `findUnique`, or catch the error and return a proper 404 instead of a raw crash.
Prisma error P2002: Unique constraint failed on the fields
P2002 means you're trying to insert or update a record with a value that already exists in a column marked `@unique`. Catch it explicitly with a try/catch and check `error.code === 'P2002'`, or query first to give the user a clear message instead of a raw 500.