Load data to MySQL, storage part of the data garbled problem

Faced with the problem of character encoding load to MySQL: It could be gbk/utf-8/or mixed code.

To ensure the atomicity of the data, the Rango solution is to convert from Python to 16, and then parse the 16 binary through MySQL parsing, which is perfect.

The cases are as follows:

Python's coded case:

>>> Import Binascii

# # # converted to 16 binary

>>> print binascii.b2a_hex (' wo Grass ')

776fe88d89

# # # converted to Kanji

>>> print Binascii.a2b_hex (' 776fe88d89 ')

Wo Grass

MySQL's anti-coding case

# # # converted to 16 binary

Mysql> Select Hex (' wo grass ');

+--------------+

| Hex (' wo Grass ') |

+--------------+

| 776fe88d89 |

+--------------+

1 row in Set (0.00 sec)

# # # converted to Kanji

Mysql> Select Unhex (' 776fe88d89 ')

;

+---------------------+

| Unhex (' 776fe88d89 ') |

+---------------------+

| Wo Grass |

+---------------------+

1 row in Set (0.00 sec)

Load data to MySQL, storage part of the data garbled problem