[Meta] Known Migrations that behave unexpectedly

[marktani]

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

Stuck Deployments

• https://github.com/graphcool/prisma/issues/2011
• https://github.com/graphcool/prisma/issues/1894
• https://github.com/graphcool/prisma/issues/2121
• https://github.com/graphcool/prisma/issues/1802
• https://github.com/graphcool/prisma/issues/2170
• Migration hangs after updating the datamodel #2118
• Changing name of relation causes infinite wait #2536
• prisma deploy is stuck when deploying two fields with same name but different casing #2793
• Deploying relation name change and explicit back relation is stuck #2906
• Any idea why my String fields are all returning 255 characters? prisma#3198
• Deploying specific datamodel with a field of type UUID is stuck #2750 (on hold)

Inconsistencies

• https://github.com/graphcool/prisma/issues/1944
• https://github.com/graphcool/prisma/issues/1687
• https://github.com/graphcool/prisma/issues/1773
• https://github.com/graphcool/prisma/issues/1640

Internal Server Errors

• https://github.com/graphcool/prisma/issues/1836
• Deploying a relation to an unknown type throws an internal server error #2871
• RedwoodJS & Netlify deploy is failing during migration prisma#2927
• Support unsigned integers in the schema prisma#3239

Misc

• https://github.com/graphcool/prisma/issues/2172

[robbyemmert]

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!

[Weakky]

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.

[marktani]

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.

[Minishlink]

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?

[terion-name]

Another stuck to the list #2490

[stale]

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.

[marktani]

Closing this, as all known issues have been fixed & released. Especially for 1.18.1, we fixed a bunch of them again.

[tanujdoshi]

Closing this, as all known issues have been fixed & released. Especially for 1.18.1, we fixed a bunch of them again.

hello , please can you help me to solve this #4625