Migration failures require manual database intervention

7/10 High

Failed migrations must be manually removed from the database, requiring write access to production. This is risky despite migrations running in transactions, and the documentation is misleading about the actual transaction behavior.

Prisma
Category
deploy
Workaround
none
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

Failed migrations, for some reason, require manually going into the database with write access to delete a failed migration entry... it seems incredibly risky to me that someone will eventually press their arrow keys too many times and end up wiping the prod database.

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