Search Results
https://dev.mysql.com/doc/refman/8.4/en/precision-math-expressions.html
With precision math, exact-value numbers are used as given whenever possible. For example, numbers in comparisons are used exactly as given without a change in value. In strict SQL mode, for INSERT into a column with an exact data type (DECIMAL or ...
https://dev.mysql.com/doc/refman/8.4/en/rebuilding-tables.html
This section describes how to rebuild or repair tables or indexes, which may be necessitated by: Changes to how MySQL handles data types or character sets. For example, an error in a collation might have been corrected, necessitating a table ...
https://dev.mysql.com/doc/refman/8.4/en/repair-table.html
[QUICK] [EXTENDED] [USE_FRM] REPAIR TABLE repairs a possibly corrupted table, for certain storage engines only. Although normally you should never have to run REPAIR TABLE, if disaster strikes, this statement is very likely to get back all your data ...
https://dev.mysql.com/doc/refman/8.4/en/replace.html
REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] { {VALUES | VALUE} (value_list) [, (value_list)] ... | VALUES row_constructor_list } REPLACE [LOW_PRIORITY | DELAYED] ...
https://dev.mysql.com/doc/refman/8.4/en/replication-encrypted-connections.html
To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica servers must support encrypted network connections. If either server does not support encrypted connections (because it ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-max-allowed-packet.html
max_allowed_packet sets an upper limit on the size of any single message between the MySQL server and clients, including replicas. If you are replicating large column values (such as might be found in TEXT or BLOB columns) and max_allowed_packet is ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-timezone.html
By default, source and replica servers assume that they are in the same time zone. If you are replicating between servers in different time zones, the time zone must be set on both source and replica. Otherwise, statements depending on the local ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-truncate.html
TRUNCATE TABLE is normally regarded as a DML statement, and so would be expected to be logged and replicated using row-based format when the binary logging mode is ROW or MIXED. However this caused issues when logging or replicating, in STATEMENT ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids.html
This section explains transaction-based replication using global transaction identifiers (GTIDs). Because GTID-based replication is completely transaction-based, it is simple to determine whether sources and replicas are consistent; as long as all ...
https://dev.mysql.com/doc/refman/8.4/en/replication-mode-change-online-verify-transactions.html
This section explains how to monitor a replication topology and verify that all anonymous transactions have been replicated. This is helpful when changing the replication mode online as you can verify that it is safe to change to GTID transactions.