PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-thread-filtering.html
For foreground threads (resulting from client connections), the initial values of the INSTRUMENTED and HISTORY columns in threads table rows are determined by whether the user account associated with a thread matches any row in the setup_actors ...
https://dev.mysql.com/doc/refman/5.7/en/multibyte-characters.html
If you want to add support for a new character set named MYSET that includes multibyte characters, you must use multibyte character functions in the ctype-MYSET.c source file in the strings directory. Look at the ctype-*.c files in the strings ...
https://dev.mysql.com/doc/refman/5.7/en/sys-sys-config-update-set-user.html
The sys_config_update_set_user trigger for the sys_config table is similar to the sys_config_insert_set_user trigger, but for UPDATE statements.
https://dev.mysql.com/doc/refman/5.7/en/charset-national.html
For example, these data type declarations are equivalent: CHAR(10) CHARACTER SET utf8 NATIONAL CHARACTER(10) NCHAR(10) As are these: VARCHAR(10) CHARACTER SET utf8 NATIONAL VARCHAR(10) NVARCHAR(10) NCHAR VARCHAR(10) NATIONAL CHARACTER VARYING(10) ...
https://dev.mysql.com/doc/refman/5.7/en/selinux-context-mysqld-tcp-port.html
If you configure mysqld to use a different TCP port, you may need to set the context for the new port. The default TCP port for mysqld is 3306; and the SELinux context type used is mysqld_port_t. For example to define the SELinux context for a ...
https://dev.mysql.com/doc/refman/5.7/en/charset-collation-compatibility.html
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 1253 (42000): COLLATION 'latin2_bin' is not valid for ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-charset.html
The following applies to replication between MySQL servers that use different character sets: If the source has databases with a character set different from the global character_set_server value, you should design your CREATE TABLE statements so ...A good workaround is to state the character set and collation explicitly in CREATE TABLE ...
https://dev.mysql.com/doc/refman/5.7/en/charset-unicode-ucs2.html
The ucs2 character set has these characteristics: Supports BMP characters only (no support for supplementary characters) Uses a fixed-length 16-bit encoding and requires two bytes per character. For example: LATIN CAPITAL LETTER A has the code ...
https://dev.mysql.com/doc/refman/5.7/en/charset-unicode-utf8.html
For more information, see Section 10.9.2, “The utf8mb3 Character Set (3-Byte UTF-8 Unicode Encoding)”.
https://dev.mysql.com/doc/refman/5.7/en/charset-unicode-utf8mb4.html
utf8mb4 contrasts with the utf8mb3 character set, which supports only BMP characters and uses a maximum of three bytes per character: For a BMP character, utf8mb4 and utf8mb3 have identical storage characteristics: same code values, same encoding, ... The utf8mb4 character set has these characteristics: Supports BMP and supplementary ...When converting utf8mb3 columns to ...