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/rename-user.html
For additional information, including how to identify which objects name a given account as the DEFINER attribute, see Orphan Stored Objects. Each account name uses the format described in Section 8.2.4, “Specifying Account Names”. (For ...
https://dev.mysql.com/doc/refman/8.0/en/repair-table.html
In the worst case, you might have a new clean index file without information about the data file, and then the next operation you perform could overwrite the data file. REPAIR PARTITION to repair one or more partitions; for more information, see ...
https://dev.mysql.com/doc/refman/8.0/en/replace.html
For information about generated columns, see Section 15.1.20.8, “CREATE TABLE and Generated Columns”. such statements produce a warning in the error log when using statement-based mode and are written to the binary log using the row-based format ... REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] { {VALUES | VALUE} (value_list) [, (value_list)] ...
https://dev.mysql.com/doc/refman/8.0/en/replica-logs-relaylog.html
Relay log files have the same format as binary log files and can be read using mysqlbinlog (see Section 6.6.9, “mysqlbinlog — Utility for Processing Binary Log Files”). For more information on binary log transaction compression, see Section ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-encryption-keys.html
The format of binary log encryption keys in the keyring is as follows: MySQLReplicationKey_{UUID}_{SEQ_NO} For example: MySQLReplicationKey_00508583-b5ce-11e8-a6a5-0010e0734796_1 {UUID} is the true UUID generated by the MySQL server (the value of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html
If you back up encrypted binary log files using mysqlbinlog, note that the copies of the files that are generated using mysqlbinlog are stored in an unencrypted format. For more information on binary log transaction compression, see Section 7.4.4.5, ... From MySQL 8.0.14, binary log files and relay log files can be encrypted, helping to protect these files and the potentially sensitive data contained in them from being misused by outside attackers, and also from unauthorized viewing by users of the operating system where they are ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-create-alter-drop-server.html
The statements CREATE SERVER, ALTER SERVER, and DROP SERVER are not written to the binary log, regardless of the binary logging format that is in use.
https://dev.mysql.com/doc/refman/8.0/en/replication-features-differing-tables.html
A column's default value is determined by a number of factors, including its type, whether it is defined with a DEFAULT option, whether it is declared as NULL, and the server SQL mode in effect at the time of its creation; for more information, see ... Source and target tables for replication do not have to be ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-functions.html
(See Section 19.2.1, “Replication Formats”.) USER() and CURRENT_USER() are automatically replicated using row-based replication when using MIXED mode, and generate a warning in STATEMENT mode. Certain functions do not replicate well under some ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-invoked.html
Note Attempting to replicate invoked features using statement-based replication produces the warning Statement is not safe to log in statement format. If you rename the events, then when demoting this server back to being a replica, you can identify ... Replication of invoked features such as loadable functions and stored programs (stored procedures and functions, triggers, and events) provides the following characteristics: The effects of the feature are always ...