Prisma1: [Meta] Known Migrations that behave unexpectedly

Created on 5 Mar 2018 · 8Comments · Source: prisma/prisma1

A collection of migrations that result in stuck deployments or other inconsistencies.

Stuck Deployments

Inconsistencies

Internal Server Errors

Misc

[x] https://github.com/graphcool/prisma/issues/2172

bu2-confirmed areengine

Source

marktani

👍4

Most helpful comment

I just have to say, Prisma is a really ambitious project, and you all get a lot of credit. Automated migrations are probably the most daunting thing about building a framework like this, but keep going, I love it!

In the mean time, do you have any recommendations on how to roll back a failed migration, or is there a recommended way to write a manual migration?

Thanks!

robbyemmert on 23 Apr 2018

❤1 👍1

All 8 comments

In the mean time, do you have any recommendations on how to roll back a failed migration, or is there a recommended way to write a manual migration?

Thanks!

robbyemmert on 23 Apr 2018

❤1 👍1

Meanwhile all these issues get solved, I advise people to never deploy without backing-up your data before, as once it happens it seems like there's no way to get out of it without prisma reset and changing the stage.

Adding

"deploy": "prisma export -p database/seed.zip && prisma deploy"

to your scripts section in the package.json is a safe work-around for now, allowing to prisma import or prisma seed whenever you have to reset prisma.

Weakky on 26 Apr 2018

Hey @robbyemmert, thanks a lot for your kind words! 🙂

In the mean time, do you have any recommendations on how to roll back a failed migration, or is there a recommended way to write a manual migration?

All migrations are kept in the internal database (can be called graphcool or prisma). There, a Migration table keeps track of all migrations.

You can cross-reference the migrations in there with the _actual_ database schema deployed for a specific service.

@Weakky, backing up your data is always a good idea 🙂But you can always patch things up manually on the database level to restore API access, and the data is not affected.

marktani on 26 Apr 2018

Hello @marktani, I'm considering prisma for new projects, and I have to say that I'm very impressed by your work, thanks and congratulations! :)

Migration is a blocker for production though, do you have documented strategies on how to workaround possible failures when deploying with a change of schema? Or does it basically boils down to do the database migration manually and prisma will adapt automatically?

Minishlink on 1 May 2018

Another stuck to the list #2490

terion-name on 22 May 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.