Rechercher dans le manuel MySQL
10.13.1 Collation Implementation Types
MySQL implements several types of collations:
Simple collations for 8-bit character sets
This kind of collation is implemented using an array of 256
weights that defines a one-to-one mapping from character codes
to weights. latin1_swedish_ci
is an example.
It is a case-insensitive collation, so the uppercase and
lowercase versions of a character have the same weights and they
compare as equal.
- Query OK, 0 rows affected (0.01 sec)
- +-------------------------+-------------------------+
- +-------------------------+-------------------------+
- | 41 | 41 |
- +-------------------------+-------------------------+
- +-----------+
- | 'a' = 'A' |
- +-----------+
- | 1 |
- +-----------+
For implementation instructions, see Section 10.13.3, “Adding a Simple Collation to an 8-Bit Character Set”.
Complex collations for 8-bit character sets
This kind of collation is implemented using functions in a C source file that define how to order characters, as described in Section 10.12, “Adding a Character Set”.
Collations for non-Unicode multibyte character sets
For this type of collation, 8-bit (single-byte) and multibyte
characters are handled differently. For 8-bit characters,
character codes map to weights in case-insensitive fashion. (For
example, the single-byte characters 'a'
and
'A'
both have a weight of
0x41
.) For multibyte characters, there are
two types of relationship between character codes and weights:
Weights equal character codes.
sjis_japanese_ci
is an example of this kind of collation. The multibyte character'ぢ'
has a character code of0x82C0
, and the weight is also0x82C0
.- Query OK, 0 rows affected (0.01 sec)
- Query OK, 3 rows affected (0.00 sec)
- +------+---------+------------------------+
- +------+---------+------------------------+
- | a | 61 | 41 |
- | A | 41 | 41 |
- | ぢ | 82C0 | 82C0 |
- +------+---------+------------------------+
Character codes map one-to-one to weights, but a code is not necessarily equal to the weight.
gbk_chinese_ci
is an example of this kind of collation. The multibyte character'膰'
has a character code of0x81B0
but a weight of0xC286
.- Query OK, 0 rows affected (0.33 sec)
- Query OK, 3 rows affected (0.00 sec)
- +------+---------+------------------------+
- +------+---------+------------------------+
- | a | 61 | 41 |
- | A | 41 | 41 |
- | 膰 | 81B0 | C286 |
- +------+---------+------------------------+
For implementation instructions, see Section 10.12, “Adding a Character Set”.
Collations for Unicode multibyte character sets
Some of these collations are based on the Unicode Collation Algorithm (UCA), others are not.
Non-UCA collations have a one-to-one mapping from character code
to weight. In MySQL, such collations are case insensitive and
accent insensitive. utf8_general_ci
is an
example: 'a'
, 'A'
,
'À'
, and 'á'
each have
different character codes but all have a weight of
0x0041
and compare as equal.
- Query OK, 0 rows affected (0.00 sec)
- Query OK, 0 rows affected (0.01 sec)
- Query OK, 4 rows affected (0.00 sec)
- +------+---------+------------------------+
- +------+---------+------------------------+
- | a | 61 | 0041 |
- | A | 41 | 0041 |
- | À | C380 | 0041 |
- | á | C3A1 | 0041 |
- +------+---------+------------------------+
UCA-based collations in MySQL have these properties:
If a character has weights, each weight uses 2 bytes (16 bits).
A character may have zero weights (or an empty weight). In this case, the character is ignorable. Example: "U+0000 NULL" does not have a weight and is ignorable.
A character may have one weight. Example:
'a'
has a weight of0x0E33
.- Query OK, 0 rows affected (0.05 sec)
- +----------+-------------------------+
- +----------+-------------------------+
- | 61 | 0E33 |
- +----------+-------------------------+
A character may have many weights. This is an expansion. Example: The German letter
'ß'
(SZ ligature, or SHARP S) has a weight of0x0FEA0FEA
.- Query OK, 0 rows affected (0.11 sec)
- +-----------+--------------------------+
- +-----------+--------------------------+
- | C39F | 0FEA0FEA |
- +-----------+--------------------------+
Many characters may have one weight. This is a contraction. Example:
'ch'
is a single letter in Czech and has a weight of0x0EE2
.- Query OK, 0 rows affected (0.09 sec)
- +-----------+--------------------------+
- +-----------+--------------------------+
- | 6368 | 0EE2 |
- +-----------+--------------------------+
A many-characters-to-many-weights mapping is also possible (this is contraction with expansion), but is not supported by MySQL.
For implementation instructions, for a non-UCA collation, see Section 10.12, “Adding a Character Set”. For a UCA collation, see Section 10.13.4, “Adding a UCA Collation to a Unicode Character Set”.
Miscellaneous collations
There are also a few collations that do not fall into any of the previous categories.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-charset-collation-implementations.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.