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
Sometimes we want to continue the migration even if certain SQL statements have error, e.g. (some tables exists on different ENV, when doing add index, it could be success on production, but fails on local).
So what do you think adding sth like --skip-failed, just like mysql --force?
The text was updated successfully, but these errors were encountered:
Sometimes we want to continue the migration even if certain SQL statements have error, e.g. (some tables exists on different ENV, when doing
add index
, it could be success on production, but fails on local).So what do you think adding sth like
--skip-failed
, just likemysql --force
?The text was updated successfully, but these errors were encountered: