Oracle 5.0 Reference Manual page 1236

Note
The
• The and
InnoDB BDB
also supports
InnoDB
• The storage engine is a "stub" engine that does nothing. You can create tables with this
EXAMPLE
engine, but no data can be stored in them or retrieved from them. The purpose of this engine is to
serve as an example in the MySQL source code that illustrates how to begin writing new storage
engines. As such, it is primarily of interest to developers.
• (also known as NDB) is the storage engine used by MySQL Cluster to implement
NDBCLUSTER
tables that are partitioned over many computers. It is available in MySQL 5.0 binary distributions.
This storage engine is currently supported on a number of Unix platforms. Experimental support for
Windows is available beginning in MySQL Cluster NDB 7.0; however, we do not intend to backport
this functionality to MySQL 5.0.
MySQL Cluster is covered in a separate chapter of this Manual. See
more information.
Note
MySQL Cluster users wishing to upgrade from MySQL 5.0 should instead
migrate to MySQL Cluster NDB 6.3, 7.0, or 7.1; these are based on MySQL
5.1 but contain the latest improvements and fixes for NDBCLUSTER. The
NDBCLUSTER
releases.
• The storage engine is used for storing large amounts of data without indexes with a very
ARCHIVE
small footprint.
• The storage engine stores data in text files using comma-separated values format.
CSV
• The storage engine accepts but does not store data and retrievals always return an
BLACKHOLE
empty set.
• The storage engine was added in MySQL 5.0.3. This engine stores data in a remote
FEDERATED
database. Currently, it works with MySQL only, using the MySQL C Client API. In future releases, we
intend to enable it to connect to other data sources using other drivers or client connection methods.
To determine which storage engines your server supports by using the
The value in the
Support
indicates that an engine is available, not available, or available and currently set as the
DEFAULT
default storage engine.
mysql> SHOW ENGINES\G
*************************** 1. row ***************************
Engine: MyISAM
Support: DEFAULT
Comment: Default engine as of MySQL 3.23 with great performance
*************************** 2. row ***************************
Engine: MEMORY
Support: YES
Comment: Hash based, stored in memory, useful for temporary tables
*************************** 3. row ***************************
Engine: InnoDB
Support: YES
Comment: Supports transactions, row-level locking, and foreign keys
*************************** 4. row ***************************
Engine: BerkeleyDB
Support: NO
Comment: Supports transactions and page-level locking
storage engine formerly was known as the
MEMORY
storage engines provide transaction-safe tables. To maintain data integrity,
referential-integrity constraints.
FOREIGN KEY
storage engine is not supported in standard MySQL 5.1
column indicates whether an engine can be used. A value of YES, NO, or
1216
engine.
HEAP
Chapter 17, MySQL Cluster, for
statement.
SHOW ENGINES