PDF (US Ltr)
- 41.8Mb
PDF (A4)
- 41.9Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/information-schema-triggers-table.html
To see information about a table's triggers, you must have the TRIGGER privilege for the table. The TRIGGERS table has these columns: TRIGGER_CATALOG The name of the catalog to which the trigger belongs. TRIGGER_SCHEMA The name of the schema ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-autocommit-commit-rollback.html
If autocommit mode is enabled, each SQL statement forms a single transaction on its own. By default, MySQL starts the session for each new connection with autocommit enabled, so MySQL does a commit after each SQL statement if that statement did not ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-best-practices.html
Specify a primary key for every table using the most frequently queried column or columns, or an auto-increment value if there is no obvious primary key. Use joins wherever data is pulled from multiple tables based on identical ID values from those ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-file-per-table-tablespaces.html
A file-per-table tablespace contains data and indexes for a single InnoDB table, and is stored on the file system in a single data file. File-per-table tablespace characteristics are described under the following topics in this section: ...
https://dev.mysql.com/doc/refman/9.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 ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-metrics-table.html
The INNODB_METRICS table provides information about InnoDB performance and resource-related counters. SET GLOBAL innodb_monitor_disable = [counter-name|module_name|pattern|all]; innodb_monitor_reset: Resets counter values to zero. SET GLOBAL ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-system-tables.html
You can extract metadata about schema objects managed by InnoDB using InnoDB INFORMATION_SCHEMA tables. Traditionally, you would get this type of information using the techniques from Section 17.17, “InnoDB Monitors”, setting up InnoDB monitors ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-understanding-innodb-locking.html
When a transaction updates a row in a table, or locks it with SELECT FOR UPDATE, InnoDB establishes a list or queue of locks on that row. Similarly, InnoDB maintains a list of locks on a table for table-level locks. If a second transaction wants to ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-migration.html
This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL instance to a larger, faster server; you might clone an entire MySQL instance to a new ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-next-key-locking.html
The so-called phantom problem occurs within a transaction when the same query produces different sets of rows at different times. For example, if a SELECT is executed twice, but returns a row the second time that was not returned the first time, ...