This is a list of MariaDB storage engines that are not distributed with MySQL. I think that most of them will work with MySQL, but not all – at least CassandraSE doesn’t.
|XtraDB||A fully-compatible fork of InnoDB, mantained by Percona||Big Bang|
|Aria||A crash-safe MyISAM, also used for internal temptables||Big Bang|
|TokuDB||A transactional engine with innovative buffers and high compression, by TokuTek||10.0|
|mroonga||Supports fulltext searches with Chinese, Japanese and Korean languages||10.0|
|SPIDER||Shards tables through multiple servers||10.0|
|OQGRAPH||Used to implement tree structures||10.0|
|Sequence||Returns a sequence of numbers as a resultset||10.0|
|CONNECT||Support several external data sources (data files, DBMS’s…)||10.0|
|CassandraSE||A bridge to Apache Cassandra||10.0|
|SphinxSE||A bridge to Sphinx||5.2|
|FederatedX||A richer fork of Federated||Big Bang|
- XtraDB is the default and should be preferred to InnoDB, unless it has a bug which affects you (but XtraDB fixes several InnoDB bugs).
- OQGRAPH was introduced during the Big Bang or soon after, but disabled in 5.5 and reintroduced in 10.0. See this post.
- FederatedX is called Federated, so it’s possible that you are already using it and you don’t know.
- CONNECT will hopefully obsolete CSV and FederatedX, but some features are still missing. For example, CONNECT cannot store NULL values in flat files.
- With MariaDB you need to specify
SQL_MODE='NO_ENGINE_SUBSTITUTION'. If you mistype the engine name, or try to use a disabled engine, you want to get an error, rather than silently switch to XtraDB.
Obsolete storage engines:
PBXT (Big Bang – 5.3) – A transactional engine which aimed to be “somewhere between InnoDB and MyISAM”. Seemed to support foreign keys better than InnoDB (I couldn’t reproduce a tirgger+FK bug and it had more options), but alas it’s dead.