MySQL Archive: Difference between revisions

Content deleted Content added

Revision as of 10:32, 19 April 2021 edit NaTRenKO (talk \| contribs) Extended confirmed users 2,819 edits m Updating Infobox (Removing unknown parameter 'status') Tag: 2017 wikitext editor ← Previous edit		Latest revision as of 00:47, 21 May 2024 edit undo Ayazkaimkhani (talk \| contribs) 3 edits No edit summary
(4 intermediate revisions by 3 users not shown)
Line 1: {{Short description\|Database engine}} {{ Infobox Software \| name = ArchiveStorage Engine Line 29 ⟶ 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 42 ⟶ 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==