Issue #38
new
Just recently I had an issue where I merged a branch and there was a migration in the merged branch that was older than the migration I had run in my current branch.
So I had missed a migration and had no way of knowing other than goose status.
It would be great to have an option to always run all the pending migrations regardless of whether they are the latest or not.
Comments (10)
-
Account Deleted
-
reporter
awesome!
-
Account Deleted
Of course, @kpuccio, this is just a proposal. I'm not really clear on the flow of goose, nor the roadmap. So. I'd really appreciate feedback from @liamstask in order to know what to improve.
-
It's awesome! I can't wait this.
-
Is there a motivation for not having 'up' also apply pending? It seems like it would simplify PR 47.
-
Account Deleted
I'm cancelling this Pull Request.
-
Why was this cancelled? This seems like basic functionality for a migration tool.
-
Account Deleted
Didn't get traction.
-
With multiple developers working on a shared database, we run into this issue frequently so we end up creating a new migration with the old DDL in it so that we can apply the migration. I feeel like
upshould do whatup_alldid in the canceled pull request. @liamstask, do you have a preferred way to make it possible to apply pending migrations? -
+1 for this PR.
- Log in to comment
I'd add the command
up_all, which will run all pending migrations. See PR 47 for feedback.