It would be interesting if Prisma would provide migration files whenever Prisma makes changes to the database. Then you could execute those database migration files to update your “prod” database. If you execute “prisma deploy” in your “prod” environment, would this break your “prod” database?

This is a great suggestion Michaël! Would you mind creating a GH issue for this concrete suggestion? Would also be interesting to hear more about your thoughts whether these migration files should be raw SQL, JS code (or other languages) or a more declarative (e.g. YML) format cc @agartha

Following

I will think about the output and will create a GH suggestion

I really like the Umzug suggestion. Thanks for pointing to that

At work we use a Go Project called Goose to do migrations. It's really nice.