Table 14.1 InnoDB Storage Engine Features
Storage limits
64TB
Transactions
Yes
Locking granularity
Row
MVCC
Yes
Geospatial data type support
Yes
Geospatial indexing support
Yes[a]
B-tree indexes
Yes
T-tree indexes
No
Hash indexes
Full-text search indexes
Yes[c]
Clustered indexes
Yes
Data caches
Yes
Index caches
Yes
Compressed data
Yes[d]
Encrypted data[e]
Yes
Cluster database support
No
Replication support[f]
Yes
Foreign key support
Yes
Backup / point-in-time recovery[g]
Yes
Query cache support
Yes
Update statistics for data dictionary
Yes
[a]InnoDB support for geospatial indexing is available in MySQL 5.7.5 and higher.
[b]InnoDB utilizes hash indexes internally for its Adaptive Hash Index feature.
[c]InnoDB support for FULLTEXT indexes is available in MySQL 5.6.4 and higher.
[d]Compressed InnoDB tables require the InnoDB Barracuda file format.
[e]Implemented in the server (via encryption functions), rather than in the storage engine.
[f]Implemented in the server, rather than in the storage engine.
[g]Implemented in the server, rather than in the storage engine.
Table 15.2 MyISAM Storage Engine Features
Storage limits
256TB
Transactions
No
Locking granularity
Table
MVCC
No
Geospatial data type support
Yes
Geospatial indexing support
Yes
B-tree indexes
Yes
T-tree indexes
No
Hash indexes
No
Full-text search indexes
Yes
Clustered indexes
No
Data caches
No
Index caches
Yes
Compressed data
Yes[a]
Encrypted data[b]
Yes
Cluster database support
No
Replication support[c]
Yes
Foreign key support
No
Backup / point-in-time recovery[d]
Yes
Query cache support
Yes
Update statistics for data dictionary
Yes
[a]Compressed MyISAM tables are supported only when using the compressed row format. Tables using the compressed row format with MyISAM are read only.
[b]Implemented in the server (via encryption functions), rather than in the storage engine.
[c]Implemented in the server, rather than in the storage engine.
[d]Implemented in the server, rather than in the storage engine.