We've updated our proposal for new migrate command...
# prisma-migrate
d
We've updated our proposal for new migrate commands. It would be great if you could have a look and give us some feedback! https://github.com/prisma/prisma/issues/10561
t
@do4gr Do you know if the new migrate commands would have helped with this issue? https://prisma.slack.com/archives/CBFFY3066/p1634333116078400
According to Frederik it sounds like it would, but I don’t know enough about the change to know for sure.
d
Yeah, i think it would help. I‘d first run „prisma migrate diff —from-migrations —to-url your-prod-url“, this should give you a summary of the differences. If those are expected you could then run that again with „—script“ to get a sql script. If you manually create a migration folder and put that script in there and then „prisma migrate resolve —applied migration-to-fix-drift“ that on your prod db you should now have a migration history that yields a db that is in line with prod.
I think this is the same as the last example command in the issue about reflecting a hotfix in prod to your migration history. Fundamentally, that is also a form of drift
Feel free to ping me once we have this out in preview then I can walk you through it with the actual cli
t
okay sounds good! Thanks!