PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/keywords.html
Certain keywords, such as SELECT, DELETE, or BIGINT, are reserved and require special treatment for use as identifiers such as table and column names. This may also be true for the names of built-in functions. Some keywords which are otherwise ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-table-compression.html
Table compression is enabled using the ROW_FORMAT=COMPRESSED attribute with CREATE TABLE or ALTER TABLE. This section describes InnoDB table compression, which is supported with InnoDB tables that reside in file_per_table tablespaces or general ...
https://dev.mysql.com/doc/refman/8.0/en/column-count-limit.html
This section describes limits on the number of columns in tables and the size of individual rows. Column Count Limits Row Size Limits Column Count Limits MySQL has hard limit of 4096 columns per table, but the effective maximum may be less for a ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-restrictions-limitations.html
This section describes restrictions and limitations of the InnoDB storage engine. You cannot create a table with a column name that matches the name of an internal InnoDB column (including DB_ROW_ID, DB_TRX_ID, and DB_ROLL_PTR. This restriction ...
https://dev.mysql.com/doc/refman/8.0/en/converting-tables-to-innodb.html
When you convert MyISAM tables that are large, frequently accessed, and hold vital data, investigate and consider the innodb_file_per_table and innodb_page_size variables, and the ROW_FORMAT and KEY_BLOCK_SIZE clauses of the CREATE TABLE statement.
https://dev.mysql.com/doc/refman/8.0/en/innodb-page-compression.html
InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Page compression is enabled by specifying the COMPRESSION attribute with CREATE TABLE or ALTER TABLE. Supported Platforms Page compression requires sparse ...
https://dev.mysql.com/doc/refman/8.0/en/create-temporary-table.html
When innodb_strict_mode is enabled (the default), CREATE TEMPORARY TABLE returns an error if ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE is specified. You can use the TEMPORARY keyword when creating a table. A TEMPORARY table is visible only within the ...
https://dev.mysql.com/doc/refman/8.0/en/dynamic-format.html
Dynamic storage format is used if a MyISAM table contains any variable-length columns (VARCHAR, VARBINARY, BLOB, or TEXT), or if the table was created with the ROW_FORMAT=DYNAMIC table option. Dynamic format is a little more complex than static ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-tuning.html
\! ls -l data/test/big_table.ibd CREATE TABLE key_block_size_4 LIKE big_table; ALTER TABLE key_block_size_4 key_block_size=4 row_format=compressed; INSERT INTO key_block_size_4 SELECT * FROM big_table; commit; -- Check how much space is needed for a ... Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-files-table.html
The FILES table provides information about the files in which MySQL tablespace data is stored. In NDB Cluster, this table also provides information about the files in which NDB Cluster Disk Data tables are stored. For additional information ...