Several rules of the "dry" MySQL Character set

The content is short but is dry, practice + theory Summary, welcome to shoot Bricks

Disclaimer: The following code does not apply to sorted sets

1) Set names and Default-character-set equivalent
2) When writing the set names (Default-character-set) than the table's character set level small can be written in, and read the time how to write how to read it will not garbled
3) The inverse process of a subset to a superset is not garbled, but it needs to be read in a subset
GBK----UTF8 (import, export)-----GBK latin1------UTF8 (import, export)-----latin1 It's not garbled.
4) UTF8-----latin1 (set names)-----UTF8 (table) storage will grow longer
5) UTF8 can be exchanged with GBK when saving Chinese characters. But still meet how (client) to save in how to read, need set names consistent to not read out garbled

This article is from the "I am White" blog, please be sure to keep this source http://10170308.blog.51cto.com/10160308/1726789

Several rules of the "dry" MySQL Character set