Rechercher dans le manuel MySQL
B.4.4.1 Case Sensitivity in String Searches
For nonbinary strings (CHAR
,
VARCHAR
,
TEXT
), string searches use the
collation of the comparison operands. For binary strings
(BINARY
,
VARBINARY
,
BLOB
), comparisons use the
numeric values of the bytes in the operands; this means that
for alphabetic characters, comparisons will be case-sensitive.
A comparison between a nonbinary string and binary string is treated as a comparison of binary strings.
Simple comparison operations (>=, >, =, <,
<=
, sorting, and grouping) are based on each
character's “sort value.” Characters with the
same sort value are treated as the same character. For
example, if e
and
é
have the same sort value in a
given collation, they compare as equal.
The default character set and collation are
utf8mb4
and
utf8mb4_0900_ai_ci
, so nonbinary string
comparisons are case insensitive by default. This means that
if you search with
, you get all column values that start with
col_name
LIKE
'a%'A
or a
. To make this
search case-sensitive, make sure that one of the operands has
a case-sensitive or binary collation. For example, if you are
comparing a column and a string that both have the
utf8mb4
character set, you can use the
COLLATE
operator to cause either operand to
have the utf8mb4_0900_as_cs
or
utf8mb4_bin
collation:
If you want a column always to be treated in case-sensitive fashion, declare it with a case-sensitive or binary collation. See Section 13.1.20, “CREATE TABLE Syntax”.
To cause a case-sensitive comparison of nonbinary strings to
be case insensitive, use COLLATE
to name a
case-insensitive collation. The strings in the following
example normally are case-sensitive, but
COLLATE
changes the comparison to be case
insensitive:
- +-----------+
- | @s1 = @s2 |
- +-----------+
- | 0 |
- +-----------+
- +--------------------------------------+
- +--------------------------------------+
- | 1 |
- +--------------------------------------+
A binary string is case-sensitive in comparisons. To compare
the string as case insensitive, convert it to a nonbinary
string and use COLLATE
to name a
case-insensitive collation:
- +--------------+
- | @s = 'mysql' |
- +--------------+
- | 0 |
- +--------------+
- +----------------------------------------------------------------+
- +----------------------------------------------------------------+
- | 1 |
- +----------------------------------------------------------------+
To determine whether a value will compare as a nonbinary or
binary string, use the
COLLATION()
function. This
example shows that VERSION()
returns a string that has a case-insensitive collation, so
comparisons are case insensitive:
- +----------------------+
- +----------------------+
- | utf8_general_ci |
- +----------------------+
For binary strings, the collation value is
binary
, so comparisons will be case
sensitive. One context in which you will see
binary
is for compression functions, which
return binary strings as a general rule: string:
- +--------------------------+
- +--------------------------+
- +--------------------------+
To check the sort value of a string, the
WEIGHT_STRING()
may be helpful.
See Section 12.5, “String Functions and Operators”.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-case-sensitivity.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.