Editing MySQL (section)

===Milestones===
Additional milestones in MySQL development included:
* First internal release on 23 May 1995
* Version 3.19: End of 1996, from www.tcx.se
* Version 3.20: January 1997
* Windows version was released on 8 January 1998 for Windows 95 and NT
* Version 3.21: production release 1998, from www.mysql.com
* Version 3.22: alpha, beta from 1998
* Version 3.23: beta from June 2000, production release 22 January 2001<ref>{{cite web|url=http://www.mysql.com/news/article-54.html |archive-url=https://web.archive.org/web/20010815175526/http://www.mysql.com/news/article-54.html |archive-date=15 August 2001 |title=MySQL 3.23 Declared Stable}}</ref>
* Version 4.0: beta from August 2002, production release March 2003 ([[Set operations (SQL)|unions]]).
* Version 4.1: beta from June 2004, production release October 2004 ([[R-tree]]s and [[B-tree]]s, subqueries, prepared statements).
* Version 5.0: beta from March 2005, production release October 2005 (cursors, stored procedures, triggers, views, [[Database transaction|XA transactions]]).
** The developer of the Federated Storage Engine states that "The Federated Storage Engine is a [[proof of concept|proof-of-concept]] storage engine",<ref>{{cite web|url=http://capttofu.livejournal.com/5798.html |title=Capttofu: FederatedX Pluggable Storage Engine Released! |publisher=Capttofu.livejournal.com |access-date=3 April 2009 |url-status=dead |archive-url=https://web.archive.org/web/20110813040439/http://capttofu.livejournal.com/5798.html |archive-date=13 August 2011}}</ref> but the main distributions of MySQL version 5.0 included it and turned it on by default. Documentation of some of the short-comings appears in "MySQL Federated Tables: The Missing Manual".<ref>{{cite web |date=8 October 2006 |title=MySQL Federated Tables: The Missing Manual |url=http://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.html |url-status=dead |access-date=1 February 2012 |publisher=O'Reilly Media |archive-date=13 August 2006 |archive-url=https://web.archive.org/web/20060813161552/http://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.html }}</ref>
* [[Sun Microsystems]] acquired MySQL AB in 2008.<ref>{{cite web |last=Arrington |first=Michael |date=2008-01-16 |title=Sun Picks Up MySQL For $1 Billion; Open Source Is A Legitimate Business Model |url=https://techcrunch.com/2008/01/16/sun-picks-up-mysql-for-1-billion-open-source-is-a-legitimate-business-model/ |access-date=13 October 2012 |website=www.techcrunch.com}}</ref>
* Version 5.1: production release 27 November 2008 (event scheduler, [[Partition (database)|partitioning]], plugin API, row-based replication, [[server log]] tables)
** Version 5.1 contained 20 known crashing and wrong result bugs in addition to the 35 present in version 5.0 ''(almost all fixed as of release 5.1.51)''.<ref>{{cite web |url=http://www.planetmysql.org/entry.php?id=16232 |title=Archives – Oops, we did it again (MySQL 5.1 released as GA with crashing bugs) |publisher=Planet MySQL |date=29 November 2008 |access-date=5 February 2013 |url-status=dead |archive-url=https://web.archive.org/web/20081230032718/http://www.planetmysql.org/entry.php?id=16232 |archive-date=30 December 2008}}</ref>
** MySQL 5.1 and 6.0-alpha showed poor performance when used for [[data warehousing]]{{snd}} partly due to its inability to utilize multiple CPU cores for processing a single query.<ref>{{cite web |author=Zaitsev |first=Peter |date=2008-04-10 |title=TPC-H Run on MySQL 5.1 and 6.0 |url=http://www.mysqlperformanceblog.com/2008/04/10/tpc-h-run-on-mysql-51-and-60/ |access-date=8 June 2009 |website=MySQL Performance Blog}}</ref>
* Oracle acquired Sun Microsystems on 27 January 2010.<ref>{{cite press release|url=http://www.oracle.com/us/corporate/press/044428 |title=Oracle Completes Acquisition of Sun|publisher=Oracle |date=27 January 2010 |access-date=1 February 2012}}</ref><ref>{{cite web |title=Overview and Frequently Asked Questions |url=https://www.oracle.com/us/assets/038563.pdf |url-status=dead |access-date=8 February 2016 |archive-date=11 February 2016 |archive-url=https://web.archive.org/web/20160211190401/https://www.oracle.com/us/assets/038563.pdf }}</ref><ref>{{cite news |last=Krill |first=Paul |date=27 January 2010 |title=Oracle's ambitious plans for integrating Sun's technology |work=InfoWorld |url=http://www.infoworld.com/article/2627785/m-a/oracle-s-ambitious-plans-for-integrating-sun-s-technology.html |access-date=2018-05-08}}</ref>
* The day Oracle announced the purchase of Sun, Michael "Monty" Widenius forked MySQL, launching [[MariaDB]], and took a swath of MySQL developers with him.<ref name="dead">{{cite news |last=Pearce |first=Rohan |date=28 March 2013 |title=Dead database walking: MySQL's creator on why the future belongs to MariaDB |work=[[Computerworld]] |url=https://www2.computerworld.com.au/article/457551/dead_database_walking_mysql_creator_why_future_belongs_mariadb/ |access-date=2020-10-02 |archive-date=3 October 2020 |archive-url=https://web.archive.org/web/20201003111459/https://www2.computerworld.com.au/article/457551/dead_database_walking_mysql_creator_why_future_belongs_mariadb/ |url-status=dead }}</ref>
[[File:Geir Høydalsvik at Percona Live Europe 2018 3.jpg|thumb|right|Geir Høydalsvik, current Senior Software Development Director for MySQL at Oracle in 2018]]
* MySQL Server 5.5 was generally available ({{as of|2010|12|lc=on}}). Enhancements and features include:
** The default storage engine is [[InnoDB]], which supports transactions and referential integrity constraints.
** Improved InnoDB I/O subsystem<ref>{{cite web|url=http://dev.mysql.com/doc/refman/5.5/en/innodb-io-changes.html|title=InnoDB I/O Subsystem Changes|publisher=dev.mysql.com|access-date=1 February 2012|url-status=dead|archive-url=https://web.archive.org/web/20120210005904/http://dev.mysql.com/doc/refman/5.5/en/innodb-io-changes.html|archive-date=10 February 2012}}</ref>
** Improved [[Symmetric multiprocessing|SMP]] support<ref>{{cite web |url=http://dev.mysql.com/doc/refman/5.5/en/smp-improvements.html |title=Scalability Improvements |publisher=dev.mysql.com |access-date=1 February 2012 |url-status=dead |archive-url=https://web.archive.org/web/20120210005914/http://dev.mysql.com/doc/refman/5.5/en/smp-improvements.html |archive-date=10 February 2012}}</ref>
** Semisynchronous replication.
** SIGNAL and RESIGNAL statement in compliance with the SQL standard.
** Support for supplementary Unicode character sets utf16, utf32, and utf8mb4.{{efn|name=utf8mb4}}
** New options for user-defined partitioning.
* MySQL Server 6.0.11-alpha was announced<ref>{{cite web |title=MySQL Lists: packagers: MySQL 6.0.11 Alpha has been released! |url=http://lists.mysql.com/packagers/418 |url-status=dead |access-date=1 February 2012 |website= |publisher=Lists.mysql.com |archive-date=23 March 2012 |archive-url=https://web.archive.org/web/20120323235154/http://lists.mysql.com/packagers/418 }}</ref> on 22 May 2009 as the last release of the 6.0 line. Future MySQL Server development uses a New Release Model. Features developed for 6.0 are being incorporated into future releases.
* The general availability of MySQL&nbsp;5.6 was announced in February 2013.<ref>{{Cite web |url=http://www.oracle.com/us/corporate/press/1904335 |title=Oracle Announces General Availability of MySQL 5.6 |access-date=13 June 2018 |archive-date=13 June 2018 |archive-url=https://web.archive.org/web/20180613191021/http://www.oracle.com/us/corporate/press/1904335 |url-status=dead }}</ref> New features included performance improvements to the [[query optimizer]], higher transactional throughput in InnoDB, new [[NoSQL]]-style memcached APIs, improvements to partitioning for querying and managing very large tables, {{mono|TIMESTAMP}} column type that correctly stores milliseconds, improvements to replication, and better performance monitoring by expanding the data available through the {{mono|PERFORMANCE_SCHEMA}}.<ref>{{cite web|url=http://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html|title=What's New in MySQL 5.6|publisher=MySQL Developer Zone|access-date=21 April 2011|url-status=dead|archive-url=https://web.archive.org/web/20110423052507/http://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html|archive-date=23 April 2011}}</ref> The InnoDB storage engine also included support for full-text search and improved group commit performance.
* The general availability of MySQL&nbsp;5.7 was announced in October 2015.<ref>{{cite web |title=Oracle Announces General Availability of MySQL 5.7 |url=https://www.oracle.com/corporate/pressrelease/mysql-5-7-ga-101915.html |url-status=dead |access-date=1 November 2015 |publisher=Oracle |archive-date=23 January 2016 |archive-url=https://web.archive.org/web/20160123022325/https://www.oracle.com/corporate/pressrelease/mysql-5-7-ga-101915.html }}</ref> As of MySQL 5.7.8, August 2015,<ref>{{Cite web |title=MySQL :: MySQL 5.7 Release Notes :: Changes in MySQL 5.7.8 (2015-08-03, Release Candidate) |url=https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-8.html#mysqld-5-7-8-json |access-date=10 October 2019 |website=dev.mysql.com}}</ref> MySQL supports a native [[JSON]] data type defined by RFC 7159.<ref>{{Cite journal|url=https://dev.mysql.com/doc/refman/5.7/en/json.html|title=MySQL :: MySQL 5.7 Reference Manual :: 11.6 The JSON Data Type|website=dev.mysql.com}}</ref><ref>{{cite IETF|year=2014 |access-date=10 October 2019|rfc=7159|editor-last1=Bray |editor-first1=T |last1=Bray |first1=T.  }}</ref>
* MySQL Server 8.0 was announced in April 2018,<ref>{{Cite web|url=https://blogs.oracle.com/mysql/announcing-general-availability-of-mysql-80|title=Announcing General Availability of MySQL 8.0|first=Mike|last=Frank|website=blogs.oracle.com|access-date=10 October 2019}}</ref> including NoSQL Document Store, atomic and crash safe DDL sentences and [[JSON]] Extended syntax, new functions, such as JSON table functions, improved sorting, and partial updates. Previous MySQL Server 8.0.0-dmr (Milestone Release) was announced 12 September 2016.<ref>{{cite web|url=http://lists.mysql.com/announce/1106 |title=8.0.0-dmr (Milestone Release) |access-date=12 September 2016}}</ref>
* MySQL was declared DBMS of the year 2019 from the [[DB-Engines ranking]]<ref>{{cite web |last=Gelbmann |first=Matthias |date=2020-01-03 |title=MySQL is the DBMS of the Year 2019 |url=https://db-engines.com/en/blog_post/83 |access-date=7 January 2020 |website=db-engines.com |publisher=DB-Engines}}</ref>