Solution to the problem of exporting data using source in mysql

The following brings you about the solution to the problem of using source to export data in mysql. I believe you must have read a similar article. What's the difference between what we bring to everyone? Let's take a look at the body. I'm sure you'll get something after reading the solution to the problem of using source to export data in mysql.

ERROR: Unknown command'\ ify.

ERROR: ASCII'\ 0' appeared in the statement, but this is not allowed unless option-- binary-mode is enabled and mysql is run in non-interactive mode. Set-- binary-mode to 1 if ASCII'\ 0' is expected. Query:?.

Baidu hurriedly learned that the sql file exported in powershell will make mistakes. Transfer the exported file to the linux CVM, and use the file command to check the result:

Little-endian UTF-16 Unicode text, with very long lines, with CRLF line terminators

Re-export the sql file information in the CVM as follows:

UTF-8 Unicode text, with very long lines

The information of the sql file exported with cmd is:

UTF-8 Unicode text, with very long lines, with CRLF line terminators

All right, powershell export file is UTF-16 encoding, cmd and linux export are UTF-8 encoding, the difference is not very clear until I check it out and then continue to write.

Last! The sql file exported by cmd source is imported into ok!

Do you think it's what you want to solve the problem above about using source to export data in mysql? If you want to know more about it, you can continue to follow our industry information section.