Feature request - Migrate: When Drift Detected -> give more Details than just the rollback script

[Jolg42]

Problem

The CLI reports some "Drift", it's not clear what it is.

Suggested solution

Provide more insight about the drift detected. Is it a column property, or entire tables that are missing?

[janpio]

Example from internal discussion: https://prisma-company.slack.com/archives/CGMCB82N8/p1617885743151100

[tomhoule]

Scheduling this for this cycle to come up with a proposal, along with related issue: https://github.com/prisma/migrations-team/issues/223

[albertoperdomo]

In the Slack thread commented above, the motivation to understand drift is for troubleshooting. The user had added a table and it was unclear to him/her, why Prisma Migrate was reporting any drift.

There are different ways this drift could be surfaced:

• abstracted: a summary of the diff, e.g. tables/columns missing, unexpected tables/columns found, difference in expected types or default values.
• detailed: a DDL script describing the changes that would required to remove the drift.

[deloreanz]

This is pretty crucial for feedback on how to resolve the issue manually. A step further could be an option to generate a migration to get the database back in line with the Prisma schema, but currently I'd be delighted just to be able to see the detected drift.

[deloreanz]

Prisma is still detecting a drift despite the fact that my Postgres structural diff detects no changes. Hopefully when more verbose detected drift feedback is available it can list exactly what it doesn't like, even when other compare tools see no diff.

[tomhoule]

prisma/prisma-engines#2002 means that the next release (and dev releases very soon) will have human-readable drift summaries. They will probably be a bit rough at the beginning, but we will improve them over time.

[Jolg42]

You can now try 2.25.0 and let us know what you think 😉