History

MariaDB was forked from MySQL after Sun's acquisition by Oracle. The project is lead by Michael Widenius, who was also a founder of MySQL AB which was later acquired by Sun. The DBMS was named after Michael Widenius' younger daughter Maria, just like MySQL, which was named after his first daughter "My".

Checkpoints[04][05]

XtraDB, a fork of InnoDB, is the default storage engine of MariaDB 10.1, while InnoDB is the default storage engine of MariaDB 10.2. InnoDB supports: Sharp checkpointing: all dirty pages of committed transactions are being flushed, while dirty pages for uncommitted transactions are not being flushed. Fuzzy checkpointing: the dirty pages that will be flushed in sharp checkpointing will be gradually flushed.

Concurrency Control[06]

InnoDB uses 2PL deadlock detection.

Data Model[07]

Foreign Keys[08]

MariaDB requires foreign keys to be checked that some integrity rules are enforced.

Indexes[09]

Different Storage engines support different indexes: Aria: B-tree, R-tree MyISAM B-tree, R-tree InnoDB: B-tree Memory/Heap: Hash, B-tree *NDB: B-tree, Hash

Isolation Levels[10]

Joins[11][12]

Logging[13][14]

Physical logging is called binary logging in MariaDB, while logical logging is called general query logging.

Query Compilation

Query Interface[15][16][17]

Storage Architecture[18]

MariaDB supports different storage architectures with different storage engines.

Storage Model[05][19]

MariaDB supports different storage models with different storage engines.

Stored Procedures[15]

Views[20]