Version sans cache

Mise en cache désactivé. Réglage défaut pour cette page : actif (code DEF204)
Si l'affichage est trop lent, vous pouvez désactiver le mode utilisateur pour visualiser la version en cache.

Rechercher dans le manuel MySQL

10.2.1 Character Set Repertoire

Table des matières

The repertoire of a character set is the collection of characters in the set.

String expressions have a repertoire attribute, which can have two values:

  • ASCII: The expression can contain only characters in the Unicode range U+0000 to U+007F.

  • UNICODE: The expression can contain characters in the Unicode range U+0000 to U+10FFFF. This includes characters in the Basic Multilingual Plane (BMP) range (U+0000 to U+FFFF) and supplementary characters outside the BMP range (U+10000 to U+10FFFF).

The ASCII range is a subset of UNICODE range, so a string with ASCII repertoire can be converted safely without loss of information to the character set of any string with UNICODE repertoire or to a character set that is a superset of ASCII. (All MySQL character sets are supersets of ASCII with the exception of swe7, which reuses some punctuation characters for Swedish accented characters.) The use of repertoire enables character set conversion in expressions for many cases where MySQL would otherwise return an “illegal mix of collations” error.

The following discussion provides examples of expressions and their repertoires, and describes how the use of repertoire changes string expression evaluation:

  • The repertoire for a string constant depends on string content and may differ from the repertoire of the string character set. Consider these statements:

    1. SET NAMES utf8; SELECT 'abc';
    2. SELECT _utf8'def';
    3. SELECT N'MySQL';

    Although the character set is utf8 in each of the preceding cases, the strings do not actually contain any characters outside the ASCII range, so their repertoire is ASCII rather than UNICODE.

  • A column having the ascii character set has ASCII repertoire because of its character set. In the following table, c1 has ASCII repertoire:

    1. CREATE TABLE t1 (c1 CHAR(1) CHARACTER SET ascii);

    The following example illustrates how repertoire enables a result to be determined in a case where an error occurs without repertoire:

    1. CREATE TABLE t1 (
    2.   c1 CHAR(1) CHARACTER SET latin1,
    3.   c2 CHAR(1) CHARACTER SET ascii
    4. );
    5. INSERT INTO t1 VALUES ('a','b');
    6. SELECT CONCAT(c1,c2) FROM t1;

    Without repertoire, this error occurs: 

    ERROR 1267 (HY000): Illegal mix of collations (latin1_swedish_ci,IMPLICIT)
and (ascii_general_ci,IMPLICIT) for operation 'concat'

    Using repertoire, subset to superset (ascii to latin1) conversion can occur and a result is returned: 

    +---------------+
| CONCAT(c1,c2) |
+---------------+
| ab            |
+---------------+

  • Functions with one string argument inherit the repertoire of their argument. The result of UPPER(_utf8'abc') has ASCII repertoire because its argument has ASCII repertoire.

  • For functions that return a string but do not have string arguments and use character_set_connection as the result character set, the result repertoire is ASCII if character_set_connection is ascii, and UNICODE otherwise:

    1. FORMAT(numeric_column, 4);

    Use of repertoire changes how MySQL evaluates the following example:

    1. SET NAMES ascii;
    2. CREATE TABLE t1 (a INT, b VARCHAR(10) CHARACTER SET latin1);
    3. INSERT INTO t1 VALUES (1,'b');
    4. SELECT CONCAT(FORMAT(a, 4), b) FROM t1;

    Without repertoire, this error occurs: 

    ERROR 1267 (HY000): Illegal mix of collations (ascii_general_ci,COERCIBLE)
and (latin1_swedish_ci,IMPLICIT) for operation 'concat'

    With repertoire, a result is returned:

    1. +-------------------------+
    2. | CONCAT(FORMAT(a, 4), b) |
    3. +-------------------------+
    4. | 1.0000b                 |
    5. +-------------------------+

  • Functions with two or more string arguments use the “widest” argument repertoire for the result repertoire (UNICODE is wider than ASCII). Consider the following CONCAT() calls:

    1. CONCAT(_ucs2 X'0041', _ucs2 X'0042')
    2. CONCAT(_ucs2 X'0041', _ucs2 X'00C2')

    For the first call, the repertoire is ASCII because both arguments are within the range of the ascii character set. For the second call, the repertoire is UNICODE because the second argument is outside the ascii character set range.

  • The repertoire for function return values is determined based only on the repertoire of the arguments that affect the result's character set and collation.

    1. IF(column1 < column2, 'smaller', 'greater')

    The result repertoire is ASCII because the two string arguments (the second argument and the third argument) both have ASCII repertoire. The first argument does not matter for the result repertoire, even if the expression uses string values.


Rechercher dans le manuel MySQL

Traduction non disponible

Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.

Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-charset-repertoire.html

L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.

Références

  1. Consulter le document html Langue du document :en Manuel MySQL : https://dev.mysql.com/

Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.

Table des matières Haut