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/problems-with-null.html
You can add an index on a column that can have NULL values if you are using the MyISAM, InnoDB, or MEMORY storage engine. The concept of the NULL value is a common source of confusion for newcomers to SQL, who often think that NULL is the same ...
https://dev.mysql.com/doc/refman/5.7/en/query-cache-operation.html
The query cache also works within transactions when using InnoDB tables. Note The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL 8.0. This section describes how the query cache works when it is operational. Section 8.10.3.3, ...
https://dev.mysql.com/doc/refman/5.7/en/rename-table.html
InnoDB interprets foreign key constraint names that begin with the string “tbl_name_ibfk_” as internally generated names. RENAME TABLE tbl_name TO new_tbl_name [, tbl_name2 TO new_tbl_name2] ... You must have ALTER and DROP privileges for the ...
https://dev.mysql.com/doc/refman/5.7/en/replace.html
(For storage engines such as InnoDB that employ row-level locking, no locking of partitions takes place.) For more information, see Section 22.6.4, “Partitioning and Locking”. REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs-status.html
If you set master_info_repository and relay_log_info_repository to TABLE, the mysql.slave_master_info and mysql.slave_relay_log_info tables are created using the InnoDB transactional storage engine. A replica server creates two replication metadata ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs.html
The mysql.slave_master_info and mysql.slave_relay_log_info tables are created using the transactional storage engine InnoDB. A replica server creates several repositories of information to use for the replication process: The relay log, which is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-errors.html
For example, since MyISAM ignores foreign key constraints, an INSERT or UPDATE statement accessing an InnoDB table on the source might cause a foreign key violation but the same statement performed on a MyISAM version of the same table on the ... If ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-failover.html
If you use InnoDB tables, you can use the mysqlbackup command from the MySQL Enterprise Backup component to produce a consistent snapshot. There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
When using GTIDs, updates to tables using nontransactional storage engines such as MyISAM cannot be made in the same statement or transaction as updates to tables using transactional storage engines such as InnoDB. Because GTID-based replication is ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-masterbaseconfig.html
Note The following options have an impact on this procedure: For the greatest possible durability and consistency in a replication setup using InnoDB with transactions, you should use innodb_flush_log_at_trx_commit=1 and sync_binlog=1 in the ... To ...