PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/charset-syntax.html
There are default settings for character sets and collations at four levels: server, database, table, and column. The description in the following sections may appear complex, but it has been found in practice that multiple-level defaulting leads ...
https://dev.mysql.com/doc/refman/8.0/en/information-functions.html
CHARSET(str) Returns the character set of the string argument, or NULL if the argument is NULL. mysql> SELECT CHARSET('abc'); -> 'utf8mb3' mysql> SELECT CHARSET(CONVERT('abc' USING latin1)); -> 'latin1' mysql> SELECT CHARSET(USER()); -> 'utf8mb3' ...
https://dev.mysql.com/doc/refman/8.0/en/charset-asian-sets.html
The Asian character sets that we support include Chinese, Japanese, Korean, and Thai. For example, the Chinese sets must allow for thousands of different characters. See Section 12.10.7.1, “The cp932 Character Set”, for additional information ...
https://dev.mysql.com/doc/refman/8.0/en/charset-baltic-sets.html
The Baltic character sets cover Estonian, Latvian, and Lithuanian languages. cp1257 (Windows Baltic) collations: cp1257_bin cp1257_general_ci (default) cp1257_lithuanian_ci latin7 (ISO 8859-13 Baltic) collations: latin7_bin latin7_estonian_cs ...
https://dev.mysql.com/doc/refman/8.0/en/charset-binary-collations.html
This section describes how the binary collation for binary strings compares to _bin collations for nonbinary strings. Binary strings (as stored using the BINARY, VARBINARY, and BLOB data types) have a character set and collation named binary.
https://dev.mysql.com/doc/refman/8.0/en/charset-ce-sets.html
MySQL provides some support for character sets used in the Czech Republic, Slovakia, Hungary, Romania, Slovenia, Croatia, Poland, and Serbia (Latin).
https://dev.mysql.com/doc/refman/8.0/en/charset-collate-precedence.html
The COLLATE clause has high precedence (higher than ||), so the following two expressions are equivalent: x || y COLLATE z x || (y COLLATE z) .
https://dev.mysql.com/doc/refman/8.0/en/charset-collate.html
With the COLLATE clause, you can override whatever the default collation is for a comparison.
https://dev.mysql.com/doc/refman/8.0/en/charset-collation-coercibility.html
In the great majority of statements, it is obvious what collation MySQL uses to resolve a comparison operation. For example, in the following cases, it should be clear that the collation is the collation of column x: SELECT x FROM T ORDER BY x; ...
https://dev.mysql.com/doc/refman/8.0/en/charset-collation-compatibility.html
Each character set has one or more collations, but 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 ...