PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/nontransactional-tables.html
If you were not deliberately mixing transactional and nontransactional tables within the transaction, the most likely cause for this message is that a table you thought was transactional actually is not. You can check the storage engine for a table ... If you receive the following message when trying to perform a ROLLBACK, it means that one or more of the tables you used in the transaction do not support transactions: Warning: Some non-transactional changed tables couldn't be rolled back These nontransactional tables are not affected by the ROLLBACK ...
https://dev.mysql.com/doc/refman/8.0/en/optimizer-trace-implementation.html
A trace is started by creating an instance of Opt_trace_start; information is added to this trace by creating instances of Opt_trace_object and Opt_trace_array, and by using the add() methods of these classes.
https://dev.mysql.com/doc/refman/8.0/en/out-of-memory.html
Is it reasonable that it should return so many rows? If not, correct the query and try again. This causes it to use the mysql_use_result() C API function to retrieve the result set, which places less of a load on the client (but more on the server).
https://dev.mysql.com/doc/refman/8.0/en/password-security.html
The following sections provide guidelines that enable end users and administrators to keep these passwords secure and avoid exposing them. In addition, the validate_password plugin can be used to enforce a policy on acceptable password.
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-stages-history-table.html
The events_stages_history table has the same columns and indexing as events_stages_current. For more information about the relationship between the three stage event tables, see Section 29.9, “Performance Schema Tables for Current and Historical ... The events_stages_history table contains the N most recent stage events that have ended per ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-statements-history-table.html
The events_statements_history table has the same columns and indexing as events_statements_current. For more information about the relationship between the three events_statements_xxx event tables, see Section 29.9, “Performance Schema Tables for ... The events_statements_history table contains the N most recent statement events that have ended per ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-transactions-history-table.html
The events_transactions_history table has the same columns and indexing as events_transactions_current. For more information about the relationship between the three transaction event tables, see Section 29.9, “Performance Schema Tables for ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-waits-history-table.html
The events_waits_history table has the same columns and indexing as events_waits_current. For more information about the relationship between the three wait event tables, see Section 29.9, “Performance Schema Tables for Current and Historical ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-firewall-groups-table.html
It lists names and operational modes of registered firewall group profiles. The firewall_groups table provides a view into the in-memory data cache for MySQL Enterprise Firewall. It is used in conjunction with the mysql.firewall_groups system table ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-keyring-keys-table.html
MySQL Server supports a keyring that enables internal server components and plugins to securely store sensitive information for later retrieval. Key metadata includes key IDs, key owners, and backend key IDs. As of MySQL 8.0.16, the keyring_keys ...