MySQL

MySQL is written in C and C++. Its SQL parser is written in yacc, but it uses a home-brewed lexical analyzer.^[17] MySQL works on many system platforms, including AIX, BSDi, FreeBSD, HP-UX, ArcaOS, eComStation, IBM i, IRIX, Linux, macOS, Microsoft Windows, NetBSD, Novell NetWare, OpenBSD, OpenSolaris, OS/2 Warp, QNX, Oracle Solaris, Symbian, SunOS, SCO OpenServer, SCO UnixWare, Sanos and Tru64. A port of MySQL to OpenVMS also exists.^[18]

The MySQL server software itself and the client libraries use dual-licensing distribution. They are offered under GPL version 2, or a proprietary license.^[19]

Support can be obtained from the official manual.^[20] Free support additionally is available in different IRC channels and forums. Oracle offers paid support via its MySQL Enterprise products. They differ in the scope of services and in price. Additionally, a number of third party organisations exist to provide support and services.

MySQL has received positive reviews, and reviewers noticed it "performs extremely well in the average case" and that the "developer interfaces are there, and the documentation (not to mention feedback in the real world via Web sites and the like) is very, very good".^[21] It has also been tested to be a "fast, stable and true multi-user, multi-threaded SQL database server".^[22]

MySQL was created by a Swedish company, MySQL AB, founded by Swedes David Axmark, Allan Larsson and Finnish Michael "Monty" Widenius.Original development of MySQL by Widenius and Axmark began in 1994.^[23] The first version of MySQL appeared on 23 May 1995. It was initially created for personal usage from mSQL based on the low-level language ISAM, which the creators considered too slow and inflexible. They created a new SQL interface, while keeping the same API as mSQL. By keeping the API consistent with the mSQL system, many developers were able to use MySQL instead of the (proprietarily licensed) mSQL antecedent.^[24]

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^[25]
• Version 4.0: beta from August 2002, production release March 2003 (unions).
• Version 4.1: beta from June 2004, production release October 2004 (R-trees and B-trees, subqueries, prepared statements).
• Version 5.0: beta from March 2005, production release October 2005 (cursors, stored procedures, triggers, views, XA transactions).
  • The developer of the Federated Storage Engine states that "The Federated Storage Engine is a proof-of-concept storage engine",^[26] 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".^[27]
• Sun Microsystems acquired MySQL AB in 2008.^[28]
• Version 5.1: production release 27 November 2008 (event scheduler, 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).^[29]
  • MySQL 5.1 and 6.0-alpha showed poor performance when used for data warehousing – partly due to its inability to utilize multiple CPU cores for processing a single query.^[30]
• Oracle acquired Sun Microsystems on 27 January 2010.^[31][32][33]
• The day Oracle announced the purchase of Sun, Michael "Monty" Widenius forked MySQL, launching MariaDB, and took a swath of MySQL developers with him.^[34]

• MySQL Server 5.5 was generally available (as of December 2010^[update]). Enhancements and features include:
  • The default storage engine is InnoDB, which supports transactions and referential integrity constraints.
  • Improved InnoDB I/O subsystem^[35]
  • Improved SMP support^[36]
  • Semisynchronous replication.
  • SIGNAL and RESIGNAL statement in compliance with the SQL standard.
  • Support for supplementary Unicode character sets utf16, utf32, and utf8mb4.^[a]
  • New options for user-defined partitioning.
• MySQL Server 6.0.11-alpha was announced^[37] 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 5.6 was announced in February 2013.^[38] 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, TIMESTAMP column type that correctly stores milliseconds, improvements to replication, and better performance monitoring by expanding the data available through the PERFORMANCE_SCHEMA.^[39] The InnoDB storage engine also included support for full-text search and improved group commit performance.
• The general availability of MySQL 5.7 was announced in October 2015.^[40] As of MySQL 5.7.8, August 2015,^[41] MySQL supports a native JSON data type defined by RFC 7159.^[42]
• MySQL Server 8.0 was announced in April 2018,^[43] 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.^[44]
• MySQL was declared DBMS of the year 2019 from the DB-Engines ranking^[45]

Release history

Work on version 6 stopped after the Sun Microsystems acquisition. The MySQL Cluster product uses version 7. The decision was made to jump to version 8 as the next major version number.^[64]

Legal disputes and acquisitions

On 15 June 2001, NuSphere sued MySQL AB, TcX DataKonsult AB and its original authors Michael ("Monty") Widenius and David Axmark in U.S District Court in Boston for "breach of contract, tortious interference with third party contracts and relationships and unfair competition".^[65][66]

In 2002, MySQL AB sued Progress NuSphere for copyright and trademark infringement in United States district court. NuSphere had allegedly violated MySQL AB's copyright by linking MySQL's GPL'ed code with NuSphere Gemini table without being in compliance with the license.^[67] After a preliminary hearing before Judge Patti Saris on 27 February 2002, the parties entered settlement talks and eventually settled.^[68] After the hearing, FSF commented that "Judge Saris made clear that she sees the GNU GPL to be an enforceable and binding license."^[69]

In October 2005, Oracle Corporation acquired Innobase OY, the Finnish company that developed the third-party InnoDB storage engine that allows MySQL to provide such functionality as transactions and foreign keys. After the acquisition, an Oracle press release mentioned that the contracts that make the company's software available to MySQL AB would be due for renewal (and presumably renegotiation) some time in 2006.^[70] During the MySQL Users Conference in April 2006, MySQL AB issued a press release that confirmed that MySQL AB and Innobase OY agreed to a "multi-year" extension of their licensing agreement.^[71]

In February 2006, Oracle Corporation acquired Sleepycat Software,^[72] makers of the Berkeley DB, a database engine providing the basis for another MySQL storage engine. This had little effect, as Berkeley DB was not widely used, and was dropped (due to lack of use) in MySQL 5.1.12, a pre-GA release of MySQL 5.1 released in October 2006.^[73]

In January 2008, Sun Microsystems bought MySQL AB for $1 billion.^[74]

In April 2009, Oracle Corporation entered into an agreement to purchase Sun Microsystems,^[75] then owners of MySQL copyright and trademark. Sun's board of directors unanimously approved the deal. It was also approved by Sun's shareholders, and by the U.S. government on 20 August 2009.^[76] On 14 December 2009, Oracle pledged to continue to enhance MySQL^[77] as it had done for the previous four years.

A movement against Oracle's acquisition of MySQL AB, to "Save MySQL"^[78] from Oracle was started by one of the MySQL AB founders, Monty Widenius. The petition of 50,000+ developers and users called upon the European Commission to block approval of the acquisition. At the same time, some Free Software opinion leaders (including Pamela Jones of Groklaw, Jan Wildeboer and Carlo Piana, who also acted as co-counsel in the merger regulation procedure) advocated for the unconditional approval of the merger.^[79][80][81] As part of the negotiations with the European Commission, Oracle committed that MySQL server will continue until at least 2015 to use the dual-licensing strategy long used by MySQL AB, with proprietary and GPL versions available. The antitrust of the EU had been "pressuring it to divest MySQL as a condition for approval of the merger". But the US Department of Justice, at the request of Oracle, pressured the EU to approve the merger unconditionally.^[82] The European Commission eventually unconditionally approved Oracle's acquisition of MySQL AB on 21 January 2010.^[83]

In January 2010, before Oracle's acquisition of MySQL AB, Monty Widenius started a GPL-only fork, MariaDB. MariaDB is based on the same code base as MySQL server 5.5 and aims to maintain compatibility with Oracle-provided versions.^[84]

MySQL is offered under two different editions: the open source MySQL Community Server^[85] and the proprietary Enterprise Server.^[86] MySQL Enterprise Server is differentiated by a series of proprietary extensions which install as server plugins, but otherwise shares the version numbering system and is built from the same code base.

Major features as available in MySQL 5.6:

• A broad subset of ANSI SQL 99, as well as extensions
• Cross-platform support
• Stored procedures, using a procedural language that closely adheres to SQL/PSM^[87]
• Triggers
• Cursors
• Updatable views
• Online Data Definition Language (DDL) when using the InnoDB Storage Engine.
• Information schema
• Performance Schema that collects and aggregates statistics about server execution and query performance for monitoring purposes.^[88]
• A set of SQL Mode options to control runtime behavior, including a strict mode to better adhere to SQL standards.
• X/Open XA distributed transaction processing (DTP) support; two phase commit as part of this, using the default InnoDB storage engine
• Transactions with savepoints when using the default InnoDB Storage Engine. The NDB Cluster Storage Engine also supports transactions.
• ACID compliance when using InnoDB and NDB Cluster Storage Engines^[89]
• SSL support
• Query caching
• Sub-SELECTs (i.e. nested SELECTs)
• Built-in replication support
  • Asynchronous replication: master-slave from one master to many slaves^[90][91] or many masters to one slave^[92]
  • Semi synchronous replication: Master to slave replication where the master waits on replication^[93][94]
  • Synchronous replication: Multi-master replication is provided in MySQL Cluster.^[95]
  • Virtual Synchronous: Self managed groups of MySQL servers with multi master support can be done using: Galera Cluster^[96] or the built in Group Replication plugin^[97]
• Full-text indexing and searching^[b]
• Embedded database library
• Unicode support^[a]
• Partitioned tables with pruning of partitions in optimizer
• Shared-nothing clustering through MySQL Cluster
• Multiple storage engines, allowing one to choose the one that is most effective for each table in the application.^[c]
• Native storage engines InnoDB, MyISAM, Merge, Memory (heap), Federated, Archive, CSV, Blackhole, NDB Cluster.
• Commit grouping, gathering multiple transactions from multiple connections together to increase the number of commits per second.

The developers release minor updates of the MySQL Server approximately every two months. The sources can be obtained from MySQL's website or from MySQL's GitHub repository, both under the GPL license.

Limitations

When using some storage engines other than the default of InnoDB, MySQL does not comply with the full SQL standard for some of the implemented functionality, including foreign key references.^[98] Check constraints are parsed but ignored by all storage engines before MySQL version 8.0.15.^[99][100]

Up until MySQL 5.7, triggers are limited to one per action / timing, meaning that at most one trigger can be defined to be executed after an INSERT operation, and one before INSERT on the same table.^[101]No triggers can be defined on views.^[101]

Before MySQL 8.0.28, inbuilt functions like UNIX_TIMESTAMP() would return 0 after 03:14:07 UTC on 19 January 2038.^[102] In 2017, an attempt to solve the problem was submitted, but was not used for the final solution that was shipped in 2022.^{[103][104][105]}

Deployment

MySQL can be built and installed manually from source code, but it is more commonly installed from a binary package unless special customizations are required. On most Linux distributions, the package management system can download and install MySQL with minimal effort, though further configuration is often required to adjust security and optimization settings.

Though MySQL began as a low-end alternative to more powerful proprietary databases, it has gradually evolved to support higher-scale needs as well. It is still most commonly used in small to medium scale single-server deployments, either as a component in a LAMP-based web application or as a standalone database server. Much of MySQL's appeal originates in its relative simplicity and ease of use, which is enabled by an ecosystem of open source tools such as phpMyAdmin.In the medium range, MySQL can be scaled by deploying it on more powerful hardware, such as a multi-processor server with gigabytes of memory.

There are, however, limits to how far performance can scale on a single server ('scaling up'), so on larger scales, multi-server MySQL ('scaling out') deployments are required to provide improved performance and reliability. A typical high-end configuration can include a powerful master database which handles data write operations and is replicated to multiple slaves that handle all read operations.^[106] The master server continually pushes binlog events to connected slaves so in the event of failure a slave can be promoted to become the new master, minimizing downtime. Further improvements in performance can be achieved by caching the results from database queries in memory using memcached, or breaking down a database into smaller chunks called shards which can be spread across a number of distributed server clusters.^[107]

High availability software

Oracle MySQL offers a high availability solution with a mix of tools including the MySQL router and the MySQL shell. They are based on Group Replication, open source tools.^[108]

MariaDB offers a similar offer in terms of products.^[109]

Cloud deployment

MySQL can also be run on cloud computing platforms such as Microsoft Azure, Amazon Elastic Compute Cloud, Oracle Cloud Infrastructure. Some common deployment models for MySQL on the cloud are:

Virtual machine image

In this implementation, cloud users can upload a machine image of their own with MySQL installed, or use a ready-made machine image with an optimized installation of MySQL on it, such as the one provided by Amazon EC2.^[110]

MySQL as a service

Some cloud platforms offer MySQL "as a service". In this configuration, application owners do not have to install and maintain the MySQL database on their own. Instead, the database service provider takes responsibility for installing and maintaining the database, and application owners pay according to their usage.^[111] Notable cloud-based MySQL services are the Amazon Relational Database Service; Oracle MySQL HeatWave Database Service, Azure Database for MySQL, Rackspace; HP Converged Cloud; Heroku and Jelastic. In this model the database service provider takes responsibility for maintaining the host and database.

Graphical user interfaces

A graphical user interface (GUI) is a type of interface that allows users to interact with electronic devices or programs through graphical icons and visual indicators such as secondary notation, as opposed to text-based interfaces, typed command labels or text navigation.

Third-party proprietary and free graphical administration applications (or "front ends") are available that integrate with MySQL and enable users to work with database structure and data visually.

MySQL Workbench

MySQL Workbench is the integrated environment for MySQL. It was developed by MySQL AB, and enables users to graphically administer MySQL databases and visually design database structures.

MySQL Workbench is available in three editions, the regular free and open source Community Edition which may be downloaded from the MySQL website, and the proprietary Standard Edition which extends and improves the feature set of the Community Edition, and the MySQL Cluster CGE.^{[112] [113]}

Other GUI tools

• Adminer
• Database Workbench
• DBeaver
• DBEdit
• HeidiSQL
• LibreOffice Base
• Navicat
• OpenOffice.org Base
• phpMyAdmin
• SQLBuddy
• SQLyog
• Toad for MySQL
• Webmin

Command-line interfaces

A command-line interface is a means of interacting with a computer program where the user issues commands to the program by typing in successive lines of text (command lines). MySQL ships with many command line tools, from which the main interface is the mysql client.^[114][115]

MySQL Utilities is a set of utilities designed to perform common maintenance and administrative tasks. Originally included as part of the MySQL Workbench, the utilities are a stand-alone download available from Oracle.

Percona Toolkit is a cross-platform toolkit for MySQL, developed in Perl.^[116] Percona Toolkit can be used to prove replication is working correctly, fix corrupted data, automate repetitive tasks, and speed up servers. Percona Toolkit is included with several Linux distributions such as CentOS and Debian, and packages are available for Fedora and Ubuntu as well. Percona Toolkit was originally developed as Maatkit, but as of late 2011, Maatkit is no longer developed.

MySQL shell is a tool for interactive use and administration of the MySQL database. It supports JavaScript, Python or SQL modes and it can be used for administration and access purposes.^[117]

Many programming languages with language-specific APIs include libraries for accessing MySQL databases. These include MySQL Connector/Net for .NET/CLI Languages,^[118] and the JDBC driver for Java.^[119]

In addition, an ODBC interface called MySQL Connector/ODBC allows additional programming languages that support the ODBC interface to communicate with a MySQL database, such as ASP or ColdFusion. The HTSQL – URL-based query method also ships with a MySQL adapter, allowing direct interaction between a MySQL database and any web client via structured URLs. Other drivers exists for languages like Python^[120] or Node.js.^[121]

A variety of MySQL forks exist, including the following.

Current

MariaDB

MariaDB is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. The fork has been led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.^[34]

Percona Server for MySQL

Percona Server for MySQL, forked by Percona, aims to retain close compatibility to the official MySQL releases.^[122] Also included in Percona Server for MySQL is XtraDB, Percona's fork of the InnoDB Storage Engine.^[123]

Abandoned

Drizzle

Drizzle was a free software/open source relational database management system (DBMS) that was forked from the now-defunct 6.0 development branch of the MySQL DBMS.^[124] Like MySQL, Drizzle had a client/server architecture and uses SQL as its primary command language. Drizzle was distributed under version 2 and 3 of the GNU General Public License (GPL) with portions, including the protocol drivers and replication messaging under the BSD license.

WebScaleSQL

WebScaleSQL was a software branch of MySQL 5.6, and was announced on 27 March 2014 by Facebook, Google, LinkedIn and Twitter as a joint effort to provide a centralized development structure for extending MySQL with new features specific to its large-scale deployments, such as building large replicated databases running on server farms. Thus, WebScaleSQL opened a path toward deduplicating the efforts each company had been putting into maintaining its own branch of MySQL, and toward bringing together more developers. By combining the efforts of these companies and incorporating various changes and new features into MySQL, WebScaleSQL aimed at supporting the deployment of MySQL in large-scale environments.^[125][126] The project's source code is licensed under version 2 of the GNU General Public License, and is hosted on GitHub.^[127][128]

OurDelta

The OurDelta distribution, created by the Australian company Open Query (later acquired by Catalyst IT Australia), had two versions: 5.0, which was based on MySQL, and 5.1, which was based on MariaDB. It included patches developed by Open Query and by other notable members of the MySQL community including Jeremy Cole and Google. Once the patches were incorporated into the MariaDB mainline, OurDelta's objectives were achieved and OurDelta passed on its build and packaging toolchain to Monty Program (now MariaDB Plc).^[129]

• Comparison of database administration tools
• Comparison of MySQL database engines
• Comparison of relational database management systems

Media related to MySQL at Wikimedia Commons

Wikibooks has more on the topic of: MySQL

• Official website
• MySQL at Oracle
• MySQL at Curlie