Problems with Chinese data in MySQL tutorial
This article mainly introduces issues related to mysql Chinese data. I hope it will be helpful to friends in need!
Recommended reference tutorial: "mysql tutorial"
The essence of Chinese data problem is the problem of character set.
Since computers only recognize binary data, and humans are more inclined to recognize characters (symbols), a correspondence between binary and characters is needed, which is Character set.
When we insert Chinese data into the server through the client of the MySQL database, it may fail. The reason may be that the character set settings of the client and the server are different, for example:
The character set of the client is
gbk
, then one Chinese character corresponds to two bytes;The character set of the server is
utf8
, one Chinese character corresponds to three bytes.
This will obviously cause problems during the encoding conversion process, resulting in failure to insert Chinese data.
Since some characteristics of all database servers are maintained through server-side variables, the system will first read its own variables to see the specific manifestations. In this case, we can use the following statement to check which character sets the server recognizes:
-- 查看服务器识别的全部字符集show character set;
Through the above query, we will find: The server is omnipotent, and its All character sets are supported.
Since the server supports so many character sets, there will always be a character set that is the server's default for dealing with clients. Therefore, we can check the server's default external processing character set through the following statement:
-- 查看服务器默认的对外处理的字符集show variables like &#Problems with Chinese data in MySQL tutorial9;character_set%&#Problems with Chinese data in MySQL tutorial9;;
Note Problems with Chinese data in MySQL tutorial: Server's default client sent The data character set is
utf8
;. Note 2: The connection layer character set is
utf8
;Annotation Problems with Chinese data in MySQL tutorial: The character set of the current database is
utf8
;Annotation Problems with Chinese data in MySQL tutorial: The server’s default character set for external processing is
utf8
.
Through the above query, we will find: The server’s default external processing character set is utf8
.
Then In turn, we are checking the character set supported by the client through the client's properties:
Obviously, we have found the source of the problem, which is indeed: Client The supported character set is gbk
, while the default character set for external processing by the server is utf8
, so there is a contradiction.
Now that the problem has been found, the solution is: Modify the default character set received by the server to gbk
.
-- 修改服务器默认接收的字符集为 GBK(不区分大小写)set character_set_client = gbk;
This way If so, when we insert Chinese data again, the insertion will be successful! But, when we checked the data, we found another problem, that is, the Chinese data we inserted before was garbled! But this is normal, because when querying, the source of the data is the server (utf8
), and the client parses the data, and the client only recognizes data in the gbk
format and displays garbled characters. That’s as expected!
Therefore, the solution is: Modify the data character set provided by the server to the client to gbk
.
-- 修改服务器给客户端的数据字符集为 GBK(不区分大小写)set character_set_results = gbk;
As shown in the picture above, the problem of inserting Chinese data into the server has been solved!
In addition, the SQL statement we used before:
-- 修改的只是会话级别,即当前客户端当次连接有效,关闭后失效set 变量 = 值;
In this case, every time we restart the client, we have to reset it in sequence, which is troublesome, so we can use the quick setting The method is:
set names 字符集;
For example,
/** * 恒等于 set character_set_client = gbk; * 恒等于 set character_set_results = gbk; * 恒等于 set character_set_connection = gbk; */set names gbk;
means that the above statement will change the values of three variables at the same time. Among them, connection
is the connection layer, which is the middleman for character set conversion. If it is consistent with the character sets of client
and results
, it will be more efficient and inconsistent. It doesn't matter either.
The above is the detailed content of Problems with Chinese data in MySQL tutorial. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Article discusses configuring SSL/TLS encryption for MySQL, including certificate generation and verification. Main issue is using self-signed certificates' security implications.[Character count: 159]

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.
