I actually think this would be super useful if we can make it make sense
(HEAD~ with merges..). "Undo the migration I just did" is a common
operation in development.
M
On 11 Mar 2016 2:18 p.m., "Joakim Saario" wrote:
> You can always have a y/N-question to limit these cases. Though, I think
> th
You can always have a y/N-question to limit these cases. Though, I think
this is a problem as it is right now too, because you can always do a typo.
/Joakim
Den fredag 11 mars 2016 kl. 14:06:42 UTC+1 skrev Markus Holtermann:
>
> Hi Joakim,
>
> thank you for your proposal.
>
> I don't think this
Hi Joakim,
thank you for your proposal.
I don't think this is a good idea because you can easily accidentally undo
too many migrations which would inevitably will result in data loss. You
don't have the data loss problem in Git as you can always recover by using
`git reflog` to go back and e.g
Hello!
Today if you just need to unmigrate the *n* migrations before the last one
you would
typically run `migrate --list` and then `migrate
` where
`migration_name` is the migration you want to roll back to.
To reduce the steps of this procedure i think it would be nice to introduce
a synta
