This section describes restrictions and limitations of the InnoDB
storage engine.
InnoDB
column (including DB_ROW_ID
, DB_TRX_ID
, and DB_ROLL_PTR
. This restriction applies to use of the names in any lettercase.mysql> CREATE TABLE t1 (c1 INT, db_row_id INT) ENGINE=INNODB;
ERROR 1166 (42000): Incorrect column name 'db_row_id'
SHOW TABLE STATUS
does not provide accurate statistics for InnoDB
tables except for the physical size reserved by the table. The row count is only a rough estimate used in SQL optimization.
InnoDB
does not keep an internal count of rows in a table because concurrent transactions might “see” different numbers of rows at the same time. Consequently, SELECT COUNT(*)
statements only count rows visible to the current transaction.
For information about how
InnoDB
processesSELECT COUNT(*)
statements, refer to theCOUNT()
description in Section 12.20.1, “Aggregate Function Descriptions”.
ROW_FORMAT=COMPRESSED
is unsupported for page sizes greater than 16KB.
A MySQL instance using a particular InnoDB
page size (innodb_page_size
) cannot use data files or log files from an instance that uses a different page size.
For limitations associated with importing tables using the Transportable Tablespaces feature, see Table Import Limitations.
For limitations associated with online DDL, see Section 14.13.6, “Online DDL Limitations”.
For limitations associated with general tablespaces, see General Tablespace Limitations.
For limitations associated with data-at-rest encryption, see Encryption Limitations.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。