Migrate in production - drift after adding data to db

Bug description

w10 - nodejs - mysql - prisma CLI - v2.23

I have a production database running locally for development and i had prisma fine and applied some migrations before After adding a new model to the schema and using CLI trying to apply it with “npx prisma migrate dev”, I got an error: "The migration ........... failed.

• Drift detected: Your database schema is not in sync with your migration history." The CLI warned that the migration cannot be added except after the problem was resolved, but I actually saw the new table being created in the db

How to reproduce

1. After 4 successful migrations
2. Added relations
3. Added data to the db
4. Edited prisma schema to add a new table
5. See error

Expected behavior

The migration to proceed adding the table without errors or the table is not created and the migration fails

Prisma information

Environment & setup

• OS: W10
• Database: MySQL
• Node.js version: v12.14.1

Prisma Version

Prisma: 2.23

[do4gr]

Hey, the proposed new commands are now out in 3.9. We’ve also included a guide how to do up and down migrations to handle failed migrations. Please check it out and let us know what you think! https://github.com/prisma/prisma/releases/tag/3.9.0

[floelhoeffel]

Hey @yazer79 - we have a proposal for some new migrate tooling that helps with failed migrations. Would be awesome if you would take a look and give us some feedback: https://github.com/prisma/prisma/issues/10561