Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "force" option to baseline #31

Open
JacksonBailey opened this issue Feb 7, 2018 · 1 comment
Open

Add "force" option to baseline #31

JacksonBailey opened this issue Feb 7, 2018 · 1 comment

Comments

@JacksonBailey
Copy link

It would be nice to be able to use a --force flag (or similar) when using the baseline functionality to drop the existing migrations table.

In our environment the migrations table seems to get messed up (or dropped or something) periodically. Why this is happening isn't the concern of this post (and I don't think it's the fault of this tool). To fix it, we can use baseline but I had to first drop the existing migrations table (migrate had been run and it failed on the first script (obviously) because the tables already existed).

@RyanSattler
Copy link

RyanSattler commented Aug 27, 2018

Yeah sometimes it would be nice to have an option to say something like "The DB is in the right state, just mark all migrations as succeeded" (in my case there was a problem when removing a comment from an already-ran migration file).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants