MySQL Archive: Difference between revisions

Revision as of 09:43, 15 November 2020

Latest revision as of 00:47, 21 May 2024

(6 intermediate revisions by 5 users not shown)

Line 1:

{{Short description|Database engine}}

{{ Infobox Software

| name = ArchiveStorage Engine

Line 8 ⟶ 9:

| developer =

| released = 2004

| status = Active

| latest release version =

| latest release date =

Line 19:

| genre = [[Database engine]]

| license = [[GNU General Public License]]

| website = http://mysql.bkbits.com

}}

Line 30:

Despite the use of [[zlib]], archive files are not compatible with [[gzio]], the basis of the [[gzip]] tools. It uses its own azio system that is a fork of gzio.

Archive differs from the other MySQL analytical engine, [[MyISAM]], by being a row -level locking engine and by keeping a constant version snapshot throughout a single query (making it [[Multiversion concurrency control|MVCC]]). This means that Archive does not lock for concurrent bulk inserts. For bulk inserts it performs an interlaced INSERT, so unlike MyISAM, order is not guaranteed.

Users can use the archive_reader tool to take an online snapshot of a table and to change the characteristics of an archive file.

Line 43:

</syntaxhighlight>

The MySQL <ref>[https://www.w3schools.blog/ MySQL Tutorial]</ref> Archive Storage Engine was authored and is maintained by [[Brian Aker]]. It was introduced in 2004 with MySQL 4.1.

==References==