PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.5Kb
Man Pages (Zip)
- 401.9Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/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/8.0/en/innodb-backup.html
Dumped tables are stored into text files that are human-readable, so spotting table corruption becomes easier. The key to safe database management is making regular backups. Hot and cold backups are physical backups that copy actual data files, ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-benefits.html
The storage layout for table data is more efficient for BLOB and long text fields, with the DYNAMIC row format. InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless of what ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-usage.html
This setting may still be useful for tables with many long BLOB, VARCHAR or TEXT columns, because such values often do compress well, and might therefore require fewer overflow pages as described in Section 17.9.1.5, “How Compression Works for ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-defragmenting.html
Another way to perform a defragmentation operation is to use mysqldump to dump the table to a text file, drop the table, and reload it from the dump file. Random insertions into or deletions from a secondary index can cause the index to become ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-space.html
LONGBLOB and LONGTEXT columns must be less than 4GB, and the total row length, including BLOB and TEXT columns, must be less than 4GB. The data files that you define in the configuration file using the innodb_data_file_path configuration option ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Key ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-developing.html
The data stored through the daemon_memcached plugin goes into VARCHAR, TEXT, or BLOB columns, and must be converted to do numeric operations. Typically, writing an application for the InnoDB memcached plugin involves some degree of rewriting or ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-intro.html
Standard memcached protocols, including the text-based protocol and the binary protocol. The InnoDB memcached plugin implements memcached as a MySQL plugin daemon that accesses the InnoDB storage engine directly, bypassing the MySQL SQL layer. The ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-table-import.html
FOR EXPORT is not supported on tables with a FULLTEXT index, as full-text search auxiliary tables cannot be flushed. After importing a table with a FULLTEXT index, run OPTIMIZE TABLE to rebuild the FULLTEXT indexes. Alternatively, drop FULLTEXT ...