Hello guys It is possible with prisma to rollback to the pre

Question

Hello guys It is possible with prisma to rollback to the previous migration Like if i added a new column by mistake then i can say that i want to rollback to the last migration or a to a migration ID Thanks

Jared · Answer

undo the commit and deploy again

José Gomes · Answer

but at certain point i will have an impossible deploy because of the data that is needed and prisma don t have default values for required fields

José Gomes · Answer

if prisma had some functionality like this a migration rollback i think it works out of the box

José Gomes · Answer

it has

Jared · Answer

with any destructive migration you are going to have to evaluate weather or not the deleted data is important Sometimes just going in the playground and manually deleting some data is enogh to make the deploy safe

José Gomes · Answer

yeap but even setting a default value for a required field the deploy cannot be done

José Gomes · Answer

and i don t want to manually do stuff

José Gomes · Answer

that destroys the workflow

Jared · Answer

`prisma deploy force` and see what the damage is

Jared · Answer

try locally first

Jared · Answer

also `prisma deploy dry run` to see whats going to happen

José Gomes · Answer

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

José Gomes · Answer

even with force

José Gomes · Answer

fieldExample String default value EXAMPLE

José Gomes · Answer

why don t prisma just set the field with the default value when deploying

José Gomes · Answer

do i really need to make the field not required then set the data for all rows and then deploy again with the required

Jared · Answer

It depends what you are aiming for running an updateall mutation might do the trick

Jared · Answer

sorry the syntax is `updateManyUsers`

José Gomes · Answer

i expected to do it without programming only editing the schema

José Gomes · Answer

i think it s kind of the main purpose here to be easy

Jared · Answer

ツ

José Gomes · Answer

i change the schema make it required set a default value and it just works

José Gomes · Answer

hm

José Gomes · Answer

but i seems that it isn t like that

José Gomes · Answer

but thanks anyway slightly smiling face

Jared · Answer

some migrations need a little help

tmoney · Answer

Tis the reason they are working on a much more robust migrations solution <https github com prisma rfcs blob migrations text 0000 migrations md>

tmoney · Answer

Couple of the proposed commands ``` prisma migrate rollback prisma migrate rollback pending ```