Misplaced Pages

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) The topic of this article may not meet Misplaced Pages's notability guidelines for products and services. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "Aria" storage engine – news · newspapers · books · scholar · JSTOR (August 2011) (Learn how and when to remove this message) This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources. Find sources: "Aria" storage engine – news · newspapers · books · scholar · JSTOR (August 2011) (Learn how and when to remove this message) This article needs to be updated. Please help update this article to reflect recent events or newly available information. (July 2014) (Learn how and when to remove this message)

Aria is a storage engine for the MariaDB and MySQL relational database management systems. Its goal is to make a crash-safe alternative to MyISAM. It is not transactional.

Aria has been in development since 2007 and was first announced by Michael "Monty" Widenius on his blog. Aria is used for internal temporary tables in MariaDB, a community-developed branch of the MySQL database led by Widenius. Aria is not shipped with MySQL or Percona Server.

Aria was initially named "Maria", as a reference to Monty's youngest child. It was renamed Aria in 2010 to avoid confusion with the main database it is developed for, MariaDB. Chris Tooley, who won a contest to suggest the name, wrote, "Aria is Maria without the 'M'; also it is a pleasant musical term."

Features

Aria is very similar to MyISAM, but its purpose is to be a crash-safe alternative to MyISAM.

Aria does not support foreign keys and, currently, transactions.

Aria supports:

• Fulltext indexes;
• OpenGIS data types;
• Virtual columns.

Files structure

Non-partitioned Aria tables consist of three physical files:

• table_name.frm
• table_name.MAD
• table_name.MAI

The .frm file contains the table definition (this file exists for all storage engines which write data to disk). The .MAD file contains the data. The .MAI file contains the indexes.

Formats

Three table formats are available for Aria tables:

• PAGE;
• FIXED;
• DYNAMIC.

PAGE is the only format available for "transactional" tables. It makes Aria tables crash-safe.

FIXED and DYNAMIC are the same formats used by MyISAM, and have been mainly implemented for compatibility. However, MyISAM's COMPRESSED format is not available in Aria.

In order to set the table format, one can use the ROW_FORMAT option in a CREATE TABLE or ALTER TABLE command.

See also

• Falcon
• InnoDB
• MyISAM
• XtraDB

References

1. Aria – AskMonty KnowledgeBase Archived May 31, 2009, at the Wayback Machine
2. "Aria FAQ - AskMonty KnowledgeBase". Archived from the original on 2010-08-22. Retrieved 2010-11-10.
3. "Rename Maria". askmonty.org. Archived from the original on 2010-05-03. Retrieved 2011-05-19.
4. "Rename Maria Contest Winner!". GNOME Blogs. Archived from the original on 2010-07-23. Retrieved 2018-01-21.

External links

• Aria in the MariaDB KnowledgeBase
• The Maria engine is released - written by Michael Widenius (founder of MySQL AB)
• Maria: The new MySQL Storage Engine at Google Videos - A talk given by Michael Widenius

This database software-related article is a stub. You can help Misplaced Pages by expanding it.

• v
• t
• e

This free and open-source software article is a stub. You can help Misplaced Pages by expanding it.

• v
• t
• e

• Database engines
• MySQL
• MariaDB
• Software using the GPL license
• Free software programmed in C++
• Database software stubs
• Free and open-source software stubs