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/replace.html
REPLACE works exactly like INSERT, except that if an old row in the table has the same value as a new row for a PRIMARY KEY or a UNIQUE index, the old row is deleted before the new row is inserted. To use REPLACE, you must have both the INSERT and ... 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/5.7/en/create-trigger.html
CREATE [DEFINER = user] TRIGGER trigger_name trigger_time trigger_event ON tbl_name FOR EACH ROW [trigger_order] trigger_body trigger_time: { BEFORE | AFTER } trigger_event: { INSERT | UPDATE | DELETE } trigger_order: { FOLLOWS | PRECEDES } ...A ...
https://dev.mysql.com/doc/refman/5.7/en/explain-output.html
Deleting all rows (JSON property: message) For DELETE, some storage engines (such as MyISAM) support a handler method that removes all table rows in a simple and fast way. No matching rows after partition pruning (JSON property: message) For DELETE ... The EXPLAIN statement provides information about how MySQL executes ...
https://dev.mysql.com/doc/refman/5.7/en/index-hints.html
They also work with multi-table DELETE statements, but not with single-table DELETE, as shown later in this section. row *************************** id: 1 select_type: DELETE table: t1 partitions: NULL type: range possible_keys: col2 key: col2 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-consistent-read.html
If another transaction deletes a row and commits after your timepoint was assigned, you do not see the row as having been deleted. If you insert or modify some rows and then commit that transaction, a DELETE or UPDATE statement issued from another ... A consistent read means that InnoDB uses multi-versioning to present to a query a snapshot of the database at a point in ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlock-example.html
Finally, client A also attempts to delete the row from the table: mysql> DELETE FROM t WHERE i = 1; Deadlock occurs here because client A needs an X lock to delete the row. The client returns this error: ERROR 1213 (40001): Deadlock found when ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-fulltext_index-tables.html
INNODB_FT_BEING_DELETED: Provides a snapshot of the INNODB_FT_DELETED table; it is used only during an OPTIMIZE TABLE maintenance operation. When OPTIMIZE TABLE is run, the INNODB_FT_BEING_DELETED table is emptied, and DOC_ID values are removed from ...For information about running OPTIMIZE TABLE on tables with FULLTEXT indexes, see Section 12.9.6, “Fine-Tuning MySQL Full-Text ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-selection.html
SQL statements supporting explicit partition selection are listed here: SELECT DELETE INSERT REPLACE UPDATE LOAD DATA. When the PARTITION option is used with DELETE statements, only those partitions (and subpartitions, if any) listed with the option ... MySQL 5.7 supports explicit selection of partitions and subpartitions that, when executing a statement, should be checked for rows matching a given WHERE ...
https://dev.mysql.com/doc/refman/5.7/en/create-table.html
Both ON DELETE and ON UPDATE actions on foreign keys are supported. Use of an explicit MATCH clause does not have the specified effect, and also causes ON DELETE and ON UPDATE clauses to be ignored. The handling of foreign key references to ...| ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-and-mysql-replication.html
It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica.