MySQL Manual
8 National Character Sets and Unicode in MySQL 4.1
- 8.3 Determining The Default Character Set And Collation
- 8.3.1 Server Character Set and Collation
- 8.3.2 Database Character Set and Collation
- 8.3.3 Table Character Set and Collation
- 8.3.4 Column Character Set and Collation
- 8.3.5 Examples of Character Set and Collation Assignment
- 8.3.6 Connection Character Sets and Collations
- 8.3.7 Character String Literal Character Set and Collation
- 8.3.8
COLLATEClause in Various Parts of an SQL Query - 8.3.9
COLLATEClause Precedence - 8.3.10
BINARYOperator - 8.3.11 Some Special Cases Where the Collation Determination is Tricky
- 8.3.12 Collations Must Be for the Right Character Set
- 8.3.13 An example of the Effect of Collation
8.3.12 Collations Must Be for the Right Character Set
Recall that each character set has one or more
collations, and each collation is associated with one and only one
character set. Therefore, the following statement
causes an error message because the latin2_bin collation is not
legal with the latin1 character set:
mysql> SELECT _latin1 'x' COLLATE latin2_bin; ERROR 1251: COLLATION 'latin2_bin' is not valid for CHARACTER SET 'latin1'
