1216
Note
The
MEMORY
storage engine formerly was known as the
HEAP
engine.
• The
InnoDB
and
BDB
storage engines provide transaction-safe tables. To maintain data integrity,
InnoDB
also supports
FOREIGN KEY
referential-integrity constraints.
• The
EXAMPLE
storage engine is a “stub” engine that does nothing. You can create tables with this
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.
•
NDBCLUSTER
(also known as
NDB
) is the storage engine used by MySQL Cluster to implement
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
Chapter 17, MySQL Cluster
, for
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
storage engine is not supported in standard MySQL 5.1
releases.
• The
ARCHIVE
storage engine is used for storing large amounts of data without indexes with a very
small footprint.
• The
CSV
storage engine stores data in text files using comma-separated values format.
• The
BLACKHOLE
storage engine accepts but does not store data and retrievals always return an
empty set.
• The
FEDERATED
storage engine was added in MySQL 5.0.3. This engine stores data in a remote
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
SHOW ENGINES
statement.
The value in the
Support
column indicates whether an engine can be used. A value of
YES
,
NO
, or
DEFAULT
indicates that an engine is available, not available, or available and currently set as the
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
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...