You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 baselinebut 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).
The text was updated successfully, but these errors were encountered:
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).
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).The text was updated successfully, but these errors were encountered: