Home Database Mysql Tutorial Problems with Chinese data in MySQL tutorial

Problems with Chinese data in MySQL tutorial

Nov 22, 2018 pm 04:30 PM

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"

Chinese data problemwith Chinese data in 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;
Copy after login

Problems with Chinese data in MySQL tutorial

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;;
Copy after login

Problems with Chinese data in MySQL tutorial

  • 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:

Problems with Chinese data in MySQL tutorial

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;
Copy after login

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;
Copy after login

Problems with Chinese data in MySQL tutorial

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 变量 = 值;
Copy after login

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 字符集;
Copy after login

For example,

/**
* 恒等于 set character_set_client = gbk;
* 恒等于 set character_set_results = gbk;
* 恒等于 set character_set_connection = gbk;
*/set names gbk;
Copy after login

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!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

When might a full table scan be faster than using an index in MySQL? When might a full table scan be faster than using an index in MySQL? Apr 09, 2025 am 12:05 AM

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.

Can I install mysql on Windows 7 Can I install mysql on Windows 7 Apr 08, 2025 pm 03:21 PM

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.

Explain InnoDB Full-Text Search capabilities. Explain InnoDB Full-Text Search capabilities. Apr 02, 2025 pm 06:09 PM

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.

Difference between clustered index and non-clustered index (secondary index) in InnoDB. Difference between clustered index and non-clustered index (secondary index) in InnoDB. Apr 02, 2025 pm 06:25 PM

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.

MySQL: Simple Concepts for Easy Learning MySQL: Simple Concepts for Easy Learning Apr 10, 2025 am 09:29 AM

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

Can mysql and mariadb coexist Can mysql and mariadb coexist Apr 08, 2025 pm 02:27 PM

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

The relationship between mysql user and database The relationship between mysql user and database Apr 08, 2025 pm 07:15 PM

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial). Apr 02, 2025 pm 07:05 PM

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

See all articles