Detailed explanation of encoding issues during MySQL command line operations

1. Check the MySQL database encoding

mysql -u username -p password show variables like 'char%'; 

2. Coding explanation

1. character_set_client: MySQL will use this encoding to interpret the data sent by the client. If the field is encoded as utf8, then if the data sent by the client is not utf8, garbled characters will appear.

2. character_set_results: MySQL will convert the data into this encoding before sending it to the client. For example, if the encoding is utf8, then if the client does not use utf8 to interpret it, garbled characters will appear.

3. Console garbled characters

3.1 Garbled characters appear when inserting or modifying

Reason: The cmd command line uses gbk encoding by default, but character_set_client is utf8.

solve:

set character_set_client = gbk;

3.2 The queried data is garbled

Reason: The cmd command line uses gbk encoding by default, but set character_set_results is utf8.

solve:

set character_set_results = gbk;

4. Specify the default encoding

The above solution is only valid for the current connection. When you exit the window, you need to set the variable again when you log in to MySQL again. Therefore, in order to solve the problem once and for all, we can set it in my.ini under the MySQL installation directory :

Just change it to gbk:

See the effect:

At this point, our MySQL encoding problem in command line operations has been successfully solved~!

Summarize

This is the end of this article about the detailed explanation of encoding issues during MySQL command line operations. For more relevant MySQL command line operation encoding content, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future!