PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/preface.html
This manual is not intended for use with older versions of the MySQL software due to the many functional and other differences between MySQL 5.7 and previous versions. This is the Reference Manual for the MySQL Database System, version 5.7, through ...
https://dev.mysql.com/doc/refman/5.7/en/replace-third-party-yum.html
mysql_upgrade also performs other functions; see Section 4.4.7, “mysql_upgrade — Check and Upgrade MySQL Tables” for details. For supported Yum-based platforms (see Section 2.5.1, “Installing MySQL on Linux Using the MySQL Yum ...
https://dev.mysql.com/doc/refman/5.7/en/replace.html
If you are using the C API, the affected-rows count can be obtained using the mysql_affected_rows() function. REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] {VALUES ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-auto-increment.html
A statement invoking a trigger or function that causes an update to an AUTO_INCREMENT column is not replicated correctly using statement-based replication. Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID(), and TIMESTAMP values is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-drop-if-exists.html
IF EXISTS statements for stored programs (stored procedures and functions, triggers, and events) are also replicated, even if the stored program to be dropped does not exist on the source. The DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS, and DROP ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-auto-positioning.html
If the replica receives transactions from more than one source, as in the case of a diamond topology, the auto-skip function ensures that the transactions are not applied twice. GTIDs replace the file-offset pairs previously required to determine ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-failover.html
As with the method using empty transactions, this method creates a server that is functionally a snapshot, but in time is able to become a source as its binary log history converges with that of the replication source server or the group. There are ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source.html
For more information on how replication channels function, see Section 16.2.2, “Replication Channels”. MySQL multi-source replication enables a replica to receive transactions from multiple immediate sources in parallel. In a multi-source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-diffengines.html
For example, in a typical scale-out scenario (see Section 16.3.4, “Using Replication for Scale-Out”), you want to use InnoDB tables on the source to take advantage of the transactional functionality, but use MyISAM on the replicas where ... It ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-performance.html
Source 2 is the replica of Source 1 that provides the replication functionality to the remainder of the replicas in the replication structure. As the number of replicas connecting to a source increases, the load, although minimal, also increases, ...