Perl inserts Chinese garbled characters into MySQL. Solution

When you use DBI to insert Chinese characters into MySQL, the text in the database will show garbled characters (even if the table is encoded as utf8). You need to add encoding settings before reading the statement before inserting the statement.

Let's talk about the character set of MySQL. In Windows, you can modify
# CLIENT SECTION
[Mysql]
Default-character-set = utf8
# SERVER SECTION
[Mysqld]
Default-character-set = utf8

These two fields are used to change the default character set of the database. The first is the default character set of the client, and the second is the default character set of the server. Suppose we set both to utf8, and then input "show variebles like" character_set _ % ";" in the MySQL Command Line Client. The following characters are displayed:

Character_set_client latin1
Character_set_connection latin1
Character_set_database utf8
Character_set_results latin1
Character_set_server utf8
Character_set_system utf8

The utf8 in it is changed with the above settings. At this point, if we read data from the database through the PHP program using the UTF-8, it is likely to be a string of Or other garbled characters. After checking for half a day on the Internet, the solution is simple. After connecting to the database and reading data, run a query "set names UTF8", that is

Mysql_query ("set names UTF8 ");
It can be displayed normally (as long as the characters in the database information are normal ). Why? In this query, what is the function of "set names UTF8?

Enter "set names UTF8;" in the MySQL command line, and then execute "show variebles like" character_set _ % ";", the original latin1 variables "character_set_client", "character_set_connection", and "character_set_results" are all changed to utf8. Refer to the manual. The above sentence is equal:

SET character_set_client = utf8;
SET character_set_results = utf8;
SET character_set_connection = utf8;

Let's take a look at the functions of the three variables:

Information input path: client & rarr; connection & rarr; server;
Information output path: server & rarr; connection & rarr; results.

In other words, each path must undergo three character set encoding changes. Taking garbled output as an example, for utf8 data in the server, the incoming connection is converted to latin1, the incoming results is converted to latin1, and the UTF-8 page is converted to results. If the two character sets are incompatible, such as latin1 and utf8, the conversion process is irreversible and destructive. So it cannot be turned back.

However, we need to declare that "set names UTF8" is only temporary, and the default value will be restored after MySQL is restarted.

Next we will talk about the configuration of MySQL on the server. Isn't it because we have to add "set names UTF8" to each database read/write to ensure data transmission encoding consistency? Can we configure MySQL to achieve the three variables which are the character set we want by default? I did not mention the manual, and I did not find the answer online. Therefore, the line of code cannot be omitted from the server configuration perspective.

Conclusion: in order to make your webpage display normally on more servers, add "set names UTF8", even if you do not add this sentence.