Reverse Migration
Hey, Is Drizzle working on the ability to reverse a migration?
https://github.com/drizzle-team/drizzle-orm/discussions/1339
I'm looking at using drizzle in our production app, but without reverse migrations we will need to build some extra release process likely with Flywheel or something that I can pump in the migration script and create a down/reverse migration script.
Before diving into this, I thought I'd check if this is something in the roadmap or coming soon to avoid creating wheels 🙂
GitHub
Migrations Rollback · drizzle-team drizzle-orm · Discussion #1339
Hi #drizzle-team & community folks đź‘‹ I'd like to suggest something that I believe more people might be looking for. Is there any plan for rollback migrations? My day-to-day workflow Because...
5 Replies
anyone?
I asked this in the #kit-discussion , too:
https://discord.com/channels/1043890932593987624/1070810929475883038/1237992331240804434
So far, it seems like this entire topic is being ignored by the team...
I get that open source maintainers don't necessarily need to do everything the community wants, but I really wish they'd be more communicative about this painpoint that seems to impact a number of community members
honestly, the lack of this feature (and the corresponding lack of communication around it) might be the sole reasons my team votes to move away from drizzle, which would be a shame
Why do you not just check out the working commit in git and run migration again?
this is not about local development for my team, but rather production
not all teams will employ a blue-green deployment strategy for their databases and it feels a bit presumptive to assume that everyone must take that approach themselves
thus, if you have a data migration that gets deployed, but misses some edge cases, you want an easy way to roll it back that's already been reviewed and deployed
alternatively, if one of the features you ship also has a migration change alongside with the code change and for whatever reason, the migration runs but the application code needs to be reverted, you need some way to quickly revert the database change as easily as possible before pushing the reverted change
I mean in production the previous deployed app and db migration version is the usable one right? So you just switch your git commit back to that version and run deploy again. Still wondering Why it doesn’t work👍