Prisma migration commands are unreliable and dangerous in non-interactive contexts

7/10 High

Prisma's migration system has multiple critical bugs: `prisma migrate dev --create-only` applies previous pending migrations unexpectedly, `migrate dev` cannot be called programmatically, and `db reset` lacks the ability to reset and reseed atomically. These issues make CI/CD integration and automated workflows fragile.

Prisma
Category
deploy
Workaround
hack
Stage
deploy
Freshness
persistent
Scope
single_lib
Upstream
open
Recurring
Yes
Buyer Type
team
Maintainer
active

Sources

Collection History

Query: “What are the most common pain points with Prisma for developers in 2025?”4/4/2026

Running `prisma migrate dev --create-only` actually applies previous (non-deployed) migrations... `migrate dev --create-only` with empty schema but existing database schema detects drift... Allow calling `prisma migrate dev` programmatically by adding `--allow-non-interactive` flag... `prisma db reset` that resets the database, pushes the schema, and runs the seed function

Created: 4/4/2026Updated: 4/4/2026