MySQL batch file continues to execute after an error

When upgrading a batch SQL script, because of the various written non-standard, non-repeatable execution, we usually want to do not abort after the SQL script error, but the completion of execution. While these issues can be performed by writing repeatable MySQL stored procedures such as add_column/drop_column, there are many times when the ready-made version requires a longer transition, so this requirement is still necessary.

It's really simple, just add the--force command line option, as follows:

Mysql-uroot-ppassword --force [db] < Patch.sql

MySQL batch file continues to execute after an error