Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Down/rollback a specific migration?
See original GitHub issueI’m submitting a…
- Bug report
- Feature request
- Question
Current behavior
Docs doesn’t mention how to rollback a specific migration.
Expected behavior
There should be a way to rollback specific migration(s).
Environment
db-migrate version: ^0.11.6 db-migrate driver with versions: db-migrate-mysql^2.1.0
Additional information:
- Node version: N/A
- Platform: N/A
Issue Analytics
- State:
- Created 4 years ago
- Comments:7
Top Results From Across the Web
Rollback one specific migration in Laravel - Stack Overflow
If you want to rollback specific migration then go to migration table and set highest value of that record in batch. Then. php...
Read more >How to rollback a specific migration | Edureka Community
Your answer will roll back the specific file. Or, simply the prefix of the migration's file name is the version you need to...
Read more >drush migrate rollback for drush 8.x
Drush migrate rollback command reference with examples for drush 8.x. ... Roll back the destination objects from a given migration
Read more >How to rollback migration in Rails - Toshimaru's Blog
Rollback specific migration You can rollback a specific migration with db:migrate:down and VERSION=xxxx .
Read more >Undo Migrations - Tutorial - Flyway
This brief tutorial will teach how to use undo migrations. It will take you through the steps on how to create and use...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
Nice. I need this behaviour too and/or invalidating single migrations rather than whole sequences. Stale-bot > People