4
The Innobase plugin provides the InnoDB storage engine. It is almost identical
5
to the innodb_plugin, but adapted to Drizzle. We plan to move to having InnoDB
6
provided by the HailDB plugin, which will allow for easier maintenance and
9
InnoDB is the default storage engine for Drizzle. It is a fully transactional
15
We maintain the Innobase plugin in Drizzle as a downstream project of the
16
innodb_plugin for MySQL. We try and keep it up to date with innodb_plugin
19
Differences from innodb_plugin
20
------------------------------
22
* AUTO_INCREMENT behaves the standard way (as in MyISAM)
23
* Supports four byte UTF-8 with the same index size
28
InnoDB supports Linux native AIO when compiled on platforms that have the
29
libaio development files installed (typically a package called libaio-dev or
30
libaio-devel). For more information on the advantages of this please see
31
http://blogs.innodb.com/wp/2010/04/innodb-performance-aio-linux/
33
To confirm that Linux native AIO is enabled execute this command:
34
"show global variables like 'innodb_use_native_aio';"
36
Compatibility with MySQL
37
------------------------
39
Although the innobase plugin is near identical to the innodb_plugin in MySQL,
40
the on disk formats are slightly incompatible (to allow for the same index
41
length for the four byte UTF-8 that Drizzle supports) and the table definitions
42
(FRM for MySQL, .dfe for Drizzle) are completely different. This means that you
43
cannot directly share InnoDB tablespaces between MySQL and Drizzle. Use the
44
drizzledump tool to migrate data from MySQL to Drizzle.