Oracle 5.0 Reference Manual page 1318

• The
InnoDB
bytes. (1024 bytes for non-64-bit builds before MySQL 5.0.17, and for all builds before 5.0.15.)
• Index key prefixes can be up to 767 bytes. See
• The maximum row length, except for variable-length columns (VARBINARY, VARCHAR,
TEXT), is slightly less than half of a database page. That is, the maximum row length is about 8000
bytes.
LONGBLOB
and
BLOB
If a row is less than half a page long, all of it is stored locally within the page. If it exceeds half a
page, variable-length columns are chosen for external off-page storage until the row fits within half a
page, as described in
• Although
row-size limit of 65,535 for the combined size of all columns:
mysql> CREATE TABLE t (a VARCHAR(8000), b VARCHAR(10000),
-> c VARCHAR(10000), d VARCHAR(10000), e VARCHAR(10000),
-> f VARCHAR(10000), g VARCHAR(10000)) ENGINE=InnoDB;
ERROR 1118 (42000): Row size too large. The maximum row size for the
used table type, not counting BLOBs, is 65535. You have to change some
columns to TEXT or BLOBs
See Section E.7.4, "Limits on Table Column Count and Row
• On some older operating systems, files must be less than 2GB. This is not a limitation of
itself, but if you require a large tablespace, you will need to configure it using several smaller data
files rather than one or a file large data files.
• The combined size of the
• The minimum tablespace size is 10MB. The maximum tablespace size is four billion database pages
(64TB). This is also the maximum size for a table.
• The default database page size in
to values ranging from 8KB to 64KB. You must update the values of
UNIV_PAGE_SIZE_SHIFT
Index Types
• tables do not support
InnoDB
• tables do not support spatial data types before MySQL 5.0.16. As of 5.0.16,
InnoDB
supports spatial data types, but not indexes on them.
Restrictions on InnoDB Tables
•
ANALYZE TABLE
output) by doing eight random dives to each of the index trees and updating index cardinality
INDEX
estimates accordingly. Because these are only estimates, repeated runs of
produce different numbers. This makes
accurate because it does not take all rows into account.
Limits on
internal maximum key length is 3500 bytes, but MySQL itself restricts this to 3072
and
LONGTEXT
columns, must be less than 4GB.
TEXT
Section 14.2.10.2, "File Space
supports row sizes larger than 65,535 bytes internally, MySQL inself imposes a
InnoDB
InnoDB
in the
Note
Changing the page size is not a supported operation and there is no
guarantee that
16KB. Problems compiling or running InnoDB may occur.
A version of
InnoDB
from a version built for a different page size.
FULLTEXT
determines index cardinality (as displayed in the
Tables
InnoDB
Section 13.1.8,
columns must be less than 4GB, and the total row length, including
Management".
log files must be less than 4GB.
is 16KB. By recompiling the code, you can set it
InnoDB
source file.
univ.i
will function normally with a page size other than
InnoDB
built for one page size cannot use data files or log files
indexes.
ANALYZE TABLE
1298
"CREATE INDEX
Size".
UNIV_PAGE_SIZE
Cardinality
ANALYZE TABLE
fast on tables but not 100%
InnoDB
Syntax".
and
BLOB
InnoDB
and
InnoDB
column of
SHOW
may