Implementation method to continue execution after MySQL batch file error _mysql

When upgrading batch SQL scripts, because of the various written nonstandard, not repeatable execution, we usually want to do not abort after the SQL script error, but execution completed. While these issues can be performed by writing repeatable MySQL stored procedures such as add_column/drop_column, many times the out-of-the-box version still requires a long 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

The above is a small series for everyone to bring the MySQL batch file after the error continues to implement the implementation of the full content, I hope that we support cloud Habitat Community ~