3 ms·
So future features notwithstanding, is the typical Prisma workflow that if a migration failed during a production deploy the developer would have to manually wo
by abaldwin99 5y ago
So future features notwithstanding, is the typical Prisma workflow that if a migration failed during a production deploy the developer would have to manually work out how to fix it while the application is down?
- tomhoule 5y agoAs of now there is no strong opinionation in the tool — you could absolutely maintain a set of down migrations to recover from bad deployments next to your regular migrations, and apply the relevant one (manually, admittedly) in case of problem.
- tor291674 5y agoTake a backup before you do any prod migrations.
- abaldwin99 5y agoSure we do that before every release as well. But a rollback is a much less invasive surgical fix compared to a full database restore. You're down while the new db instance spins up and any writes in the meantime will be lost. You can also test migrations against a restored prod database snapshot but again there's no guarantee some incompatible data hasn't been inserted in the meantime.