The default encoding of MySQL is Latin1, which does not support Chinese characters. You need to change the default encoding of the database to GBK or utf8 at noon.
1. You need to log in as the root user to view the database encoding method (the command for logging in as the root user is:> mysql-u root-P, enter the password of the root user twice), and the database encoding command is:> show variables like 'character % ';
+ -------------------------- + ---------------------------- +
| Variable_name | value |
+ -------------------------- + ---------------------------- +
| Character_set_client | Latin1 |
| Character_set_connection | Latin1 |
| Character_set_database | Latin1 |
| Character_set_filesystem | binary |
| Character_set_results | Latin1 |
| Character_set_server | Latin1 |
| Character_set_system | utf8 |
| Character_sets_dir |/usr/share/MySQL/charsets/|
+ -------------------------- + Bytes + from the above information, we can see that the database code is Latin1 and needs to be modified to GBK or utf8. character_set_client is the client encoding method, and character_set_connection is the encoding used for establishing; character_set_database database encoding; character_set_results result set encoding; character_set_server Database Server encoding; as long as the above four encoding methods are the same, there will be no garbled problem. Another command for viewing database encoding:> show variables like 'collation % '; 2. in Linux, change the default encoding of MySQL database to: u to stop MySQL running.
/Etc/init. d/MySQL start (STOP) is to start and stop the server. U MySQL master configuration file is my. CNF. The common directory is/etc/mysqlvar/lib/MySQL/, where the database table folder is placed, here, MySQL is equivalent to the date folder of MySQL in windows. When we need to modify the default encoding of the MySQL database, we need to edit my. CNF file for encoding modification. in Linux, modify the MySQL configuration file my. CNF, default file location/etc/My. CNF File
Find the client configuration [client] and add it below
Default-character-set = utf8 default Character Set: utf8
Add in [mysqld]
Default-character-set = utf8 default Character Set: utf8
Init_connect = 'set names utf8' (utf8 encoding is used to set the connection to the MySQL database to run utf8)
After modification, restart MySQL and re-query the database encoding to find the encoding method changed:
> Show variables like 'character % ';
+ -------------------------- + ---------------------------- +
| Variable_name | value |
+ -------------------------- + ---------------------------- +
| Character_set_client | utf8 |
| Character_set_connection | utf8 |
| Character_set_database | utf8 |
| Character_set_filesystem | binary |
| Character_set_results | utf8 |
| Character_set_server | utf8 |
| Character_set_system | utf8 |
| Character_sets_dir |/usr/share/MySQL/charsets/|
+ -------------------------- + ---------------------------- +
This method is also effective for the standard MySQL version, for/etc/My. CNF file, from the MySQL/support-Files Folder CP my-large.cnf to/etc/My. CNF 3. In Windows, you can delete the MySQL database and reinstall it, you can directly use MySQL server instance config wizard during installation. 4. You can specify the database encoding method when the MySQL database server has data that is not suitable for deletion and reinstallation. The encoding method specified by MySQL is flexible and diverse. You can specify the table-level encoding, row-level encoding, or even field-level encoding. The following example shows two ways to specify encoding when creating a database: 1) Create Database ms_db Character Set utf8 collate utf8_general_ci; 2) create database if not exists netctoss default Character Set utf8; 5. If you are using external access, you can determine the Request Encoding format in the connection, for example, JDBC: mysql: // localhost: 3306/MySQL? Useunicode = true & characterencoding = UTF-8 (Note: Do not see any space, otherwise error) 6. Run the Script: Specify the encoding format set names GBK (note, not a UTF-8) before you can modify the execution: after execution: we can see from the execution before and after the command that set names GBK can only modify the encoding methods of character_set_client, character_set_connection, and character_set_results. This modification is window-level and only valid for this window, the modification in another window is invalid. We can also find that the encoding method at the underlying layer of the database has not changed, and the data is still maintained by UTF-8 encoding after being inserted. Address: http://helloworlda.iteye.com/blog/1275160
