Prisma Error P2004: Constraint Failed on the Database

Quick Answer

Read error.meta.database_error - the raw database message is the most specific clue. If that does not apply, look for CHECK/enum/exclude constraints in your schema or migrations that the value violates — the full checklist is below.

Error Code

Error code: P2004
Official name: Constraint Failed on the Database
Service: Prisma

What does this error mean?

A constraint failed on the database: {database_error}

Common Causes

• A database-level CHECK constraint rejecting a value (e.g. price > 0)
• An enum column receiving a value outside the declared enum
• A PostgreSQL EXCLUDE constraint or other custom constraint violation
• Database-specific type errors surfaced as a generic constraint failure

How to Fix

1. Read error.meta.database_error - the raw database message is the most specific clue
2. Look for CHECK/enum/exclude constraints in your schema or migrations that the value violates
3. If the error came from raw SQL ($queryRaw), verify the SQL against the actual column types
4. Align the Prisma schema with the database: run prisma migrate dev after changing constraints

Code Examples

catch (e) {
  if (e.code === 'P2004') {
    console.error(e.meta.database_error)
  }
}

Framework-Specific Fixes

if (e.code === 'P2004') {
  return response.status(400).json({
    message: 'Constraint violation',
    detail: e.meta.database_error,
  })
}

model Order {
  status Status @default(PENDING)
}
enum Status { PENDING PAID CANCELLED }

You Might Also Like

Frequently Asked Questions

Recommended Tools

Recommendations are editorial — DB Error Reference takes no payment or affiliate fees for tool listings.

Official Sources

This page is based on the official Prisma documentation linked below and adds practical troubleshooting guidance on top.

• Prisma Client and Prisma Migrate errors (Error Reference)official