Migration creation based on dev database instead of schema history

6/10 Medium

Prisma creates migrations by comparing the development database to the schema, not based on previous migrations. This causes issues when developers switch branches with different schemas and forget to reset their local database.

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

Migration creation also happens by looking at your development database and comparing it to your Prisma schema, instead of your previous migrations. This is another design decision which I don't agree with, as local dev database schemas can vary branch to branch.

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