Is anyone using Prisma in Production and dealing with the HUGE required field migrations flaw?

I think you are talking about promotion of non required field to required field. To get rid of that you will require to set value for all of the rows otherwise we can't set the constraint. This is a manual process right now We know this is frustrating right now and we may enable a sensible defaults for migrations: https://github.com/prisma/prisma/issues/2323 We are also working on a new migrations api: https://github.com/prisma/rfcs/blob/migrations/text/0000-migrations.md