Prisma · prisma migrate
Drift detected: database schema is not in sync with migration history
Drift detected: Your database schema is not in sync with your migration history.
We need to reset the "public" schema at "localhost:5432"
You may use prisma migrate reset to drop the development database.
All data will be lost.What it means
prisma migrate dev compared the database to the migrations folder and they disagree: something changed the database outside a migration.
Common causes
- The agent ran prisma db push on a database that also uses migrate
- Someone edited a table by hand in the provider's dashboard
- A migration file was edited or deleted after it was applied
How to fix it
- On a dev database with throwaway data, let migrate reset it
- Never answer yes on a database with real data: back it up, then create a migration for the difference (prisma migrate diff) or baseline
- Pick one workflow per database: db push for prototypes, migrate for anything in production
Prompt for Cursor or Claude Code
prisma migrate dev reports drift and wants to reset the database. Don't confirm the reset. Tell me what changed (compare with prisma migrate diff), whether this database has real data, and the safe way to get back in sync. Use migrations only from now on.Not quite your error? Paste yours into the free VibeBoot Doctor or browse the Prisma error fixer.
next: skip the next one
Skip the setup. The VibeBoot SaaS Starter ships a ready prisma/schema.prisma and one Prisma client in src/lib/db.ts (SQLite by default, Postgres by changing the provider), plus auth and Stripe on Next.js 16.4.3. $49, one-time.
14-day money-back guarantee · lifetime updates
Other Prisma errors
$ fixed it? get the next one first
New fixes for what AI agents break, by email.
When we add a fix or a Cursor rule for a new Next.js, Auth.js, Prisma or Stripe break, it goes out in the VibeBoot newsletter. Free, occasional, unsubscribe in one click.