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/precision-math-decimal-characteristics.html
The format is explained (with an example) in the decimal2bin() function. This section discusses the characteristics of the DECIMAL data type (and its synonyms), with particular regard to the following topics: Maximum number of digits Storage format ...
https://dev.mysql.com/doc/refman/8.0/en/prepare.html
Beginning with MySQL 8.0.22, a parameter used in a prepared statement has its type determined when the statement is first prepared, and retains this type whenever EXECUTE is invoked for this prepared statement (unless the statement is reprepared, as ... PREPARE stmt_name FROM preparable_stmt The PREPARE statement prepares a SQL statement and assigns it a name, stmt_name, by which to refer to the statement ...
https://dev.mysql.com/doc/refman/8.0/en/replication-channels.html
Each replication channel must have a unique (nonempty) name, as explained in Section 19.2.2.4, “Replication Channel Naming Conventions”. In MySQL multi-source replication, a replica opens multiple replication channels, one for each source ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-differing-tables.html
It is also possible to specify whether or not to permit lossy (truncated) or non-lossy conversions of demoted column values, as explained later in this section. Source and target tables for replication do not have to be identical. A table on the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-functions.html
To explain the potential problems when replicating between servers which are in different time zones, suppose that the source is located in New York, the replica is located in Stockholm, and both servers are using local time. Certain functions do ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html
This section explains how to avoid inconsistencies and solve any problems they cause. Inconsistencies in the sequence of transactions that have been executed from the relay log can occur depending on your replication configuration. A transaction ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-assign-anon.html
If the replica server is started without GTIDs enabled and with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS set for any replication channels, the settings are not changed, but a warning message is written to the error log explaining how to change the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-failover.html
This section explains how to avoid fetching all of the execution history from the source by copying binary log files to the new server. There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-lifecycle.html
It also ensures that the filtered-out transactions are not retrieved again if the replica reconnects to the source, as explained in Section 19.1.3.3, “GTID Auto-Positioning”. The life cycle of a GTID consists of the following steps: A ...
https://dev.mysql.com/doc/refman/8.0/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 ...