You are creating a required field but there are already nodes present that would violate that constraint

I know that this is an "expected behaviour" that adding required fields with default doesn't work, but how this can be worked around?

Modify data -> deploy

manually add columns in db?)

If you are creating new you can setup default value

it is set in schema – it doesn't work

you can make workaround 🙂 deploy without required and then add data

run a graphql mutation through the playground to add your data. eg:

updateManyX(where:{ newField:null }, data: { newField: newValue })

(using the process huv1k described tho !)

so without manual work this is impossible. not able to properly deploy anything with CI/CD.. terrifying.

Please join the #migrations working group and provide your input, we are currently designing a new migration system that keeps the simplicity/UX of the current migration system while handling the different migrations that are currently a bit tricky in a robust and straight forward way 🙂

@terion i rly don't get you, because prisma is still in development its not finished product and you expect to handle every edge case?