Jump to content

MySQL: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m →{{anchor|FABRIC|HA}}High availability: Removed broken reference, as requested by the ReferenceBot.
Awfief (talk | contribs)
65 edits
Took out opinions and FUD; the man pages being proprietary was a bug, and MariaDB was founded long before Oracle bought Sun (and therefore MySQL).
Line 172: Line 172:


==Community==
==Community==
The MySQL server software itself and the client libraries use [[dual license|dual-licensing]] distribution. They are offered under GPL version 2,<ref>{{cite web|url=http://www.mysql.com/products/licensing/opensource-license.html |title=Oracle :: MySQL Open Source License |publisher=Mysql.com |date= |accessdate=8 June 2009}}</ref> beginning from 28 June 2000<ref>{{cite web|url=http://www.mysql.com/news/article-23.html |archiveurl=http://web.archive.org/web/20010812012244/http://www.mysql.com/news/article-23.html |archivedate=12 August 2001 |title=MySQL GOES GPL}}</ref> (which in 2009 has been extended with a [[Alternative terms for free software|FLOSS]] License Exception)<ref>{{cite web|url=http://www.mysql.com/company/legal/licensing/foss-exception.html |title=Oracle :: FLOSS License Exception |publisher=Mysql.com |date= |accessdate=8 June 2009}}</ref> or to use a proprietary license.<ref>{{cite web|url=http://www.mysql.com/company/legal/licensing/commercial-license.html |title=Oracle :: MySQL Commercial License |publisher=Mysql.com |date= |accessdate=8 June 2009}}</ref> In 2013, the Linux man pages for MySQL switched to a proprietary license<ref>{{cite web|url=https://blog.mariadb.org/mysql-man-pages-silently-relicensed-away-from-gpl/ |title=MySQL man pages silently relicensed away from GPL |publisher=MariaDB Foundation |date=18 June 2013 |accessdate=18 June 2013}}</ref> temporarily due to a build system bug. The original GPL license has since been restored.<ref>{{cite web|url= http://bugs.mysql.com/bug.php?id=69512 |title=MySQL Bugs: #69512: Wrong license in man pages in Community Server |publisher=Oracle bugtracking system |date=19 June 2013 |accessdate=25 June 2013}}</ref>
The MySQL server software itself and the client libraries use [[dual license|dual-licensing]] distribution. They are offered under GPL version 2,<ref>{{cite web|url=http://www.mysql.com/products/licensing/opensource-license.html |title=Oracle :: MySQL Open Source License |publisher=Mysql.com |date= |accessdate=8 June 2009}}</ref> beginning from 28 June 2000<ref>{{cite web|url=http://www.mysql.com/news/article-23.html |archiveurl=http://web.archive.org/web/20010812012244/http://www.mysql.com/news/article-23.html |archivedate=12 August 2001 |title=MySQL GOES GPL}}</ref> (which in 2009 has been extended with a [[Alternative terms for free software|FLOSS]] License Exception)<ref>{{cite web|url=http://www.mysql.com/company/legal/licensing/foss-exception.html |title=Oracle :: FLOSS License Exception |publisher=Mysql.com |date= |accessdate=8 June 2009}}</ref> or to use a proprietary license.<ref>{{cite web|url=http://www.mysql.com/company/legal/licensing/commercial-license.html |title=Oracle :: MySQL Commercial License |publisher=Mysql.com |date= |accessdate=8 June 2009}}</ref>


Support can be obtained from the official manual.<ref>[http://dev.mysql.com/doc/refman/5.5/en/index.html MySQL Support Manual], MySQL Developers</ref> 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, including SkySQL Ab and Percona.
Support can be obtained from the official manual.<ref>[http://dev.mysql.com/doc/refman/5.5/en/index.html MySQL Support Manual], MySQL Developers</ref> 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, including SkySQL Ab and Percona.
Line 180: Line 180:
===Related projects===
===Related projects===
* [[Drizzle (database server)|Drizzle]]&nbsp;– a fork targeted at the web-infrastructure and cloud computing markets. The developers of the product describe it as a "smaller, slimmer and (hopefully) faster version of MySQL". As a result, many common MySQL features will be stripped out, including stored procedures, query cache, prepared statements, views, and triggers. This is a partial rewrite of the server that does not maintain compatibility with MySQL.
* [[Drizzle (database server)|Drizzle]]&nbsp;– a fork targeted at the web-infrastructure and cloud computing markets. The developers of the product describe it as a "smaller, slimmer and (hopefully) faster version of MySQL". As a result, many common MySQL features will be stripped out, including stored procedures, query cache, prepared statements, views, and triggers. This is a partial rewrite of the server that does not maintain compatibility with MySQL.
* [[MariaDB]]&nbsp;– a community-developed fork of the MySQL database source code, the impetus being the community maintenance of its free status under GPL as opposed to any uncertainty of MySQL license status under its current ownership by Oracle.<ref>&ldquo;The opposing camp believes that Oracle purchased MySQL only to kill it.&rdquo; &mdash; Bryan Richard, [http://www.linux-mag.com/id/7309/ &ldquo;Oracle Buys SUN; MySQL is Forked&rdquo;], [http://www.linux-mag.com ''Linux Magazine''], 2009 April 20 (retrieved 2014 June 17)</ref><ref>&ldquo;The [European] commission may be exploring whether Oracle will continue to develop MySQL as an open-source database, said Patrick Walravens, an analyst at JMP Securities in San Francisco.&rdquo; &mdash; Peter Chapman and Matthew Newman, [http://www.bloomberg.com/apps/news?pid=newsarchive&sid=aCWYuHl5bHC8 &ldquo;Oracle Faces In-Depth EU Probe Over Sun Purchase&rdquo;] at [http://www.bloomberg.com Bloomberg], 2009 September 3 (retrieved 2014 June 17)</ref><ref>&ldquo;[https://mariadb.com/kb/en/what-is-the-goal-of-mariadb/ What is the goal of MariaDB?] To provide a community developed, stable, and <u>always Free</u> branch of MySQL that is, on the user level, compatible with the main version.&rdquo; (emphasis added), at [https://mariadb.com mariadb.com]</ref> The intent also being to maintain high fidelity with MySQL, ensuring a "drop-in" replacement capability with library binary equivalency and exact matching with MySQL APIs and commands. It includes the [[XtraDB]] storage engine as a replacement for InnoDB.
* [[MariaDB]]&nbsp;– a community-developed fork of the MySQL database source code. [https://mariadb.com/kb/en/what-is-the-goal-of-mariadb/ What is the goal of MariaDB?] To provide a community developed, stable, and always free branch of MySQL that is, on the user level, compatible with the main version.&rdquo; at [https://mariadb.com mariadb.com]</ref> The intent also being to maintain high fidelity with MySQL, ensuring a "drop-in" replacement capability with library binary equivalency and exact matching with MySQL APIs and commands. It includes the [[XtraDB]] storage engine as a replacement for InnoDB.
* [[Percona Server]]&nbsp;– a fork of MySQL that includes the XtraDB storage engine. Its policy is to deviate as little as possible from MySQL and remain fully compatible, while providing new features, better performance, and additional instrumentation for analysis of performance and usage.<ref>{{cite web
* [[Percona Server]]&nbsp;– a fork of MySQL that includes the XtraDB storage engine. Its policy is to deviate as little as possible from MySQL and remain fully compatible, while providing new features, better performance, and additional instrumentation for analysis of performance and usage.<ref>{{cite web
| url = http://www.mysqlperformanceblog.com/2009/08/13/xtradb-the-top-10-enhancements/
| url = http://www.mysqlperformanceblog.com/2009/08/13/xtradb-the-top-10-enhancements/

Revision as of 02:32, 20 June 2014

Original author(s)MySQL AB
Developer(s)Oracle Corporation
Initial release23 May 1995; 29 years ago (1995-05-23)
Stable release
5.6.19[1] / 30 May 2014; 10 years ago (2014-05-30)
Preview release
5.7.4[2] / 31 March 2014; 10 years ago (2014-03-31)
Repository
Written inC, C++[3]
Operating systemWindows, Linux, Solaris, OS X, FreeBSD[4]
Available inEnglish
TypeRDBMS
LicenseGPL (version 2) or commercial[5]
Websitewww.mysql.com

MySQL (/maɪ ˌɛskjuːˈɛl/ "My S-Q-L",[6] officially, but also called /maɪ ˈsiːkwəl/ "My Sequel") is (as of March 2014) the world's second most[nb 1] widely used[9][10] open-source relational database management system (RDBMS).[11] It is named after co-founder Michael Widenius's daughter, My.[12] The SQL phrase stands for Structured Query Language.[6]

The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Oracle Corporation.[13]

MySQL is a popular choice of database for use in web applications, and is a central component of the widely used LAMP open source web application software stack (and other 'AMP' stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open source projects that require a full-featured database management system often use MySQL.

For commercial use, several paid editions are available, and offer additional functionality. Applications which use MySQL databases include: TYPO3, MODx, Joomla, WordPress, phpBB, MyBB, Drupal and other software. MySQL is also used in many high-profile, large-scale websites, including Wikipedia,[14] Google[15][16] (though not for searches), Facebook,[17][18][19] Twitter,[20] Flickr,[21] and YouTube.[22]

Interfaces

MySQL Workbench running on OS X

MySQL is a relational database management system (RDBMS), and ships with no GUI tools to administer MySQL databases or manage data contained within the databases. Users may use the included command line tools,[23][24] or use MySQL "front-ends", desktop software and web applications that create and manage MySQL databases, build database structures, back up data, inspect status, and work with data records.[25][26][27][28] The official set of MySQL front-end tools, MySQL Workbench is actively developed by Oracle, and is freely available for use.[29]

Graphical

The official MySQL Workbench is a free integrated environment developed by MySQL AB, that enables users to graphically administer MySQL databases and visually design database structures. MySQL Workbench replaces the previous package of software, MySQL GUI Tools. Similar to other third-party packages, but still considered the authoritative MySQL front end, MySQL Workbench lets users manage database design & modeling, SQL development (replacing MySQL Query Browser) and Database administration (replacing MySQL Administrator).

MySQL Workbench is available in two 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.

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. Some well-known front ends, in alphabetical order, are:

  • Adminer – a free MySQL front end written in one PHP script, capable of managing multiple databases, with many CSS skins available.
  • DBEdit – a free front end for MySQL and other databases.
  • HeidiSQL – a full featured free front end that runs on Windows, and can connect to local or remote MySQL servers to manage databases, tables, column structure, and individual data records. Also supports specialised GUI features for date/time fields and enumerated multiple-value fields.[30]
  • LibreOffice Base – LibreOffice Base allows the creation and management of databases, preparation of forms and reports that provide end users easy access to data. Like Microsoft Access, it can be used as a front-end for various database systems, including Access databases (JET), ODBC data sources, and MySQL or PostgreSQL.[31]
  • Navicat – a series of proprietary graphical database management applications, developed for Windows, Macintosh and Linux.
  • OpenOffice.org – OpenOffice.org Base can manage MySQL databases if the entire suite is installed. Free and open-source.
  • phpMyAdmin – a free Web-based front end widely installed[citation needed] by web hosts, since it is developed in PHP and is included in the LAMP stack, MAMP, XAMPP and WAMP software bundle installers.
  • Webmin – a free Web-based management utility and a MySQL front end, developed in Perl with some parts written in Java.
  • SQLBuddy – a free Web-based front end, developed in PHP.
  • SQLyog – commercial, but there is also a free 'community' edition available.
  • Toad for MySQL – a free development and administration front end for MySQL from Quest Software
  • Chive – is a free, open source, web-based database management tool designed as an alternative to phpMyAdmin.

Other available proprietary MySQL front ends include dbForge Studio for MySQL, DBStudio, Epictetus, Microsoft Access, Oracle SQL Developer, SchemaBank, SQLPro SQL Client, Toad Data Modeler and DaDaBIK.

Command line

MySQL ships with many command line tools, from which the main interface is 'mysql' client.[23][24] Third-parties have also developed tools to manage MySQL servers.

  • MySQL Utilities – a set of utilities designed to perform common maintenance and administrative tasks. Originally included as part of the MySQL Workbench, the utilities are now a stand-alone download available from Oracle.
  • Percona Toolkit – a cross-platform toolkit for MySQL, developed in Perl.[32] 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.

Programming

MySQL works on many system platforms, including AIX, BSDi, FreeBSD, HP-UX, eComStation, i5/OS, IRIX, Linux, OS X, 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.[33]

MySQL is written in C and C++. Its SQL parser is written in yacc, but it uses a home-brewed lexical analyzer.[34] Many programming languages with language-specific APIs include libraries for accessing MySQL databases. These include MySQL Connector/Net for integration with Microsoft's Visual Studio (languages such as C# and VB are most commonly used) and the JDBC driver for Java. In addition, an ODBC interface called MyODBC 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.

Features

As of April 2009, MySQL offered MySQL 5.1 in two different variants: the open source MySQL Community Server and the commercial Enterprise Server. MySQL 5.5 is offered under the same licenses.[35] They have a common code base and include the following features:

  • 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[36]
  • Triggers
  • Cursors
  • Updatable views
  • Information schema
  • Strict mode (ensures MySQL does not truncate or otherwise modify data to conform to an underlying data type, when an incompatible value is inserted into that type)
  • X/Open XA distributed transaction processing (DTP) support; two phase commit as part of this, using Oracle's InnoDB engine
  • Independent storage engines (MyISAM for read speed, InnoDB for transactions and referential integrity, MySQL Archive for storing historical data in little space)
  • Transactions with the InnoDB and NDB Cluster storage engines; savepoints with InnoDB
  • SSL support
  • Query caching
  • Sub-SELECTs (i.e. nested SELECTs)
  • Replication support (i.e. Master-Master Replication & Master-Slave Replication) with one master per slave, many slaves per master.[37] Multi-master replication is provided in MySQL Cluster,[38] and multi-master support can be added to unclustered configurations using Galera Cluster.[39]
  • Full-text indexing and searching (initially a MyISAM-only feature; supported by InnoDB since the release of MySQL 5.6)
  • Embedded database library
  • Unicode support (however prior to 5.5.3 UTF-8 and UCS-2 encoded strings are limited to the BMP, in 5.5.3 and later use utf8mb4 for full unicode support)
  • ACID compliance when using transaction capable storage engines (InnoDB and Cluster)[40]
  • 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 (in MySQL 5.0, storage engines must be compiled in; in MySQL 5.1, storage engines can be dynamically loaded at run time):
  • Commit grouping, gathering multiple transactions from multiple connections together to increase the number of commits per second. (PostgreSQL has an advanced form of this functionality[42])

The developers release monthly versions of the MySQL Server. The sources can be obtained from MySQL's website or from MySQL's Bazaar repository, both under the GPL license.

Limitations

Like other SQL databases, MySQL does not currently comply with the full SQL standard for some of the implemented functionality, including foreign key references when using some storage engines other than the 'standard' InnoDB (or third-party engines which supports foreign keys).[43]

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.[44] No triggers can be defined on views.[44]

MySQL, like most other transactional relational databases, is strongly limited by hard disk performance. This is especially true in terms of write latency.[45] Given the recent appearance of very affordable consumer grade SATA interface solid-state drives that offer zero mechanical latency, a fivefold speedup over even an eight drive RAID array can be had for a smaller investment.[46][47]

MySQL database's inbuilt functions like UNIX_TIMESTAMP() will return 0 after 03:14:07 UTC on 19 January 2038.[48]

Deployment

The LAMP software bundle (here additionally with Squid). A high performance and high-availability solution for a hostile environment

MySQL can be built and installed manually from source code, but this can be tedious so 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.[49] The master server synchronizes continually with its 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.[50]

Backup

  • Filesystem snapshot or volume manager snapshot – backups are performed by using an external tool provided by the operating system (such as LVM) or storage device, with additional support from MySQL for ensuring consistency of such snapshots.
  • mysqldump – a logical backup tool included with both community and enterprise editions of MySQL. Supports backup from all storage engines.
  • MySQL Enterprise Backup – a hot backup utility included as part of the MySQL Enterprise subscription from Oracle. Offers native InnoDB hot backup, as well as backup for other storage engines.
  • XtraBackup – open source MySQL hot backup software. Some notable features include hot, non-locking backups for InnoDB storage, incremental backups, streaming, parallel-compressed backups, throttling based on the number of I/O operations per second, etc.[51]

High availability

Ensuring high availability requires a certain amount of redundancy in the system. For database systems, the redundancy traditionally takes the form of having a primary server acting as a master, and using replication to keep secondaries available to take over in case the primary fails. This means that the "server" that the application connects to is in reality a collection of servers, not a single server. In a similar manner, if the application is using a sharded database, it is in reality working with a collection of servers, not a single server. In this case, a collection of servers is usually referred to as a farm.[52]

One of the projects aiming to provide high availability for MySQL is MySQL Fabric, an integrated system for managing a collection of MySQL servers, and a framework on top of which high availability and database sharding is built. MySQL Fabric is open-source and is intended to be extensible, easy to use, and to support procedure execution even in the presence of failure, providing an execution model usually called resilient execution. MySQL client libraries are extended so they are hiding the complexities of handling failover in the event of a server failure, as well as correctly dispatching transactions to the shards. As of September 2013, there is currently support for Fabric-aware versions of Connector/J, Connector/PHP, Connector/Python, as well as some rudimentary support for Hibernate and Doctrine. As of May 2014, MySQL Fabric is in the general availability stage of development.[53]

Cloud deployment

Main article: Cloud database

MySQL can also be run on cloud computing platforms such as Amazon EC2. Listed below are some common deployment models for MySQL on the cloud:

  • Virtual Machine Image – 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.[54]
  • 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.[55] Notable cloud-based MySQL services are the Amazon Relational Database Service; Rackspace; HP Converged Cloud; Heroku and Jelastic.
  • Managed MySQL cloud hosting – the database is not offered as a service, but the cloud provider hosts the database and manages it on the application owner's behalf. As of 2011, of the major cloud providers, only Terremark and Rackspace offer managed hosting for MySQL databases.[56][57]

Community

The MySQL server software itself and the client libraries use dual-licensing distribution. They are offered under GPL version 2,[58] beginning from 28 June 2000[59] (which in 2009 has been extended with a FLOSS License Exception)[60] or to use a proprietary license.[61]

Support can be obtained from the official manual.[62] 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, including SkySQL Ab and Percona.

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".[63] It has also been tested to be a "fast, stable and true multi-user, multi-threaded sql database server".[64]

  • Drizzle – a fork targeted at the web-infrastructure and cloud computing markets. The developers of the product describe it as a "smaller, slimmer and (hopefully) faster version of MySQL". As a result, many common MySQL features will be stripped out, including stored procedures, query cache, prepared statements, views, and triggers. This is a partial rewrite of the server that does not maintain compatibility with MySQL.
  • MariaDB – a community-developed fork of the MySQL database source code. What is the goal of MariaDB? To provide a community developed, stable, and always free branch of MySQL that is, on the user level, compatible with the main version.” at mariadb.com</ref> The intent also being to maintain high fidelity with MySQL, ensuring a "drop-in" replacement capability with library binary equivalency and exact matching with MySQL APIs and commands. It includes the XtraDB storage engine as a replacement for InnoDB.
  • Percona Server – a fork of MySQL that includes the XtraDB storage engine. Its policy is to deviate as little as possible from MySQL and remain fully compatible, while providing new features, better performance, and additional instrumentation for analysis of performance and usage.[65][66]
  • OurDelta – No longer maintained. It was a fork compiled with various patches, including patches from MariaDB, Percona, and Google, and a storage engine called OQGRAPH.
  • WebScaleSQL – A branch of MySQL 5.6 maintained by Facebook, LinkedIn, Google and Twitter.[67]

History

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. 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 (commercially licensed) mSQL antecedent.[citation needed][dubious – discuss]

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".[68][69]

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

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.[73] During the MySQL Users Conference in April 2006, MySQL issued a press release that confirmed that MySQL and Innobase OY agreed to a "multi-year" extension of their licensing agreement.[74]

In February 2006, Oracle Corporation acquired Sleepycat Software,[75] 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.[76]

In January 2008, Sun Microsystems bought MySQL for $1 billion.[77]

In April 2009, Oracle Corporation entered into an agreement to purchase Sun Microsystems,[78] 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.[79] On 14 December 2009, Oracle pledged to continue to enhance MySQL[80] as it had done for the previous four years.

A movement against Oracle's acquisition of MySQL, to "Save MySQL"[81] from Oracle was started by one of the MySQL 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, several Free Software opinion leaders (including Eben Moglen, 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.[citation needed] 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 commercial 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, as revealed by WikiLeaks, the US Department of Justice and Antitrust, at the request of Oracle, pressured the EU to unconditionally approve the merger.[82] The European Commission eventually unconditionally approved Oracle's acquisition of MySQL on 21 January 2010.[83]

In January 2009, prior to Oracle's acquisition of MySQL, Monty Widenius started a GPL-only fork, MariaDB. MariaDB is based on the same code base as MySQL server 5.1 and strives to maintain compatibility with Oracle-provided versions.[84]

Oracle holds back test cases for bug fixes, but functionality test suites are still published. This is an Oracle policy to prevent accidentally releasing CVE crashing test cases. In August 2012, TechCrunch's Alex Williams reported that Oracle was holding back MySQL Server test cases, a move that he concluded indicated that Oracle is attempting to kill the product.[85] Percona also reported that Oracle is no longer synchronizing their changes with the public source repositories.[86] Widenius called this a breach of the agreement that Oracle entered into with the EU as a condition of their acquisition of Sun.[87]

In April 2013, Wikipedia announced that it had completed the migration of the English and German Wikipedias as well as Wikidata to MariaDB 5.5.[88] Google has also said they will be switching to MariaDB.[89][90]

Linux distributions Red Hat,[91] Fedora,[92] OpenSUSE,[citation needed] Slackware[93] and Arch Linux[94] have announced that they are switching to MariaDB by default, while Ubuntu has stated that it will be sticking with MySQL. Mark Shuttleworth has stated, "As for phobias, the real pitchforks have been those agitating against Oracle. I think Oracle have been an excellent steward of MySQL, with real investment and great quality."[95] Other Linux distributions are offering MariaDB as an option.[96][97][98]

Milestones

Notable milestones in MySQL development include:

  • Original development of MySQL by Michael Widenius and David Axmark beginning in 1994[99]
  • 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[100]
  • Version 4.0: beta from August 2002, production release March 2003 (unions)
  • Version 4.01: beta from August 2003, Jyoti[clarification needed][citation needed] adopts MySQL for database tracking
  • 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",[101] 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".[102]
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).[104]
MySQL 5.1 and 6.0 showed poor performance when used for data warehousing — partly due to its inability to utilize multiple CPU cores for processing a single query.[105]
  • Oracle acquired Sun Microsystems on 27 January 2010.[106]
  • MySQL Server 5.5 is currently generally available (as of December 2010). Enhancements and features include:
    • The default storage engine is InnoDB, which supports transactions and referential integrity constraints.
    • Improved InnoDB I/O subsystem[107]
    • Improved SMP support[108]
    • Semisynchronous replication.
    • SIGNAL and RESIGNAL statement in compliance with the SQL standard.
    • Support for supplementary Unicode character sets utf16, utf32, and utf8mb4.
    • New options for user-defined partitioning.
  • MySQL Server 6.0.11-alpha was announced[109] 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.
  • MySQL 5.6 general availability was announced in February 2013. New features include 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.[110] The InnoDB storage engine now also supports full text search and improved group commit performance.
  • MySQL 5.7 Development Milestone 3 was released December 2013.[111]

Versions

The following chart provides an overview of various MySQL versions and their current development statuses:[112][113][114][115][116][117][118][119]

See also

Notes

  1. ^ Following SQLite, which is deployed with every iPhone and Android device along with the Chrome and Firefox browsers.[7] In the second quarter of 2013 alone, 213 million smartphones shipped, of which 200 million were Android and iOS.[8]

References

  1. ^ "Changes in MySQL 5.6.19". MySQL 5.6 Reference Manual. Oracle. 30 May 2014. Retrieved 30 May 2014.
  2. ^ "Changes in Release 5.7.4 (Development)". MySQL 5.7 Reference Manual. Oracle Corporation. 31 March 2014. Retrieved 2 April 2014.
  3. ^ "MySQL: Project Summary". Ohloh. Black Duck Software. Retrieved 17 September 2012.
  4. ^ "Supported Platforms: MySQL Database". Oracle. Retrieved 24 March 2014.
  5. ^ http://www.mysql.com/downloads/
  6. ^ a b "What is MySQL?". MySQL 5.1 Reference Manual. Oracle. Retrieved 17 September 2012. The official way to pronounce "MySQL" is "My Ess Que Ell" (not "my sequel")
  7. ^ "Well-Known Users of SQLite". The SQLite Consortium. Retrieved 8 October 2013. Apple uses SQLite for many functions within Mac OS X, including Apple Mail, Safari, and in Aperture. Apple uses SQLite in the iPhone and in the iPod touch and in iTunes software. .... SQLite is the primary meta-data storage format for the Firefox Web Browser and the Thunderbird Email Reader from Mozilla. .... It is known that Google uses SQLite in their Desktop for Mac, in Google Gears, in the Android cell-phone operating system, and in the Google Chrome Web Browser.
  8. ^ Koetsier, John (1 August 2013). "Android reaches massive 80% market share, Windows Phone hits global high, iPhone languishes Read more at http://venturebeat.com/2013/08/01/android-reaches-massive-80-market-share-windows-phone-hits-global-high-iphone-languishes". MobileBeat. VentureBeat. Retrieved 8 October 2013. Global smartphone shipments grew 47 percent to hit 230 million devices in the second quarter of 2013, according to a new report from research firm Strategy Analytics. Android captured record market share of 80 percent, while iOS hit a new low of 14 percent. {{cite web}}: External link in |title= (help)
  9. ^ "Market Share". Why MySQL?. Oracle. Retrieved 17 September 2012.
  10. ^ "DB-Engines Ranking". Retrieved 29 July 2013.
  11. ^ Schumacher, Robin; Lentz, Arjen. "Dispelling the Myths". MySQL AB. Archived from the original on 6 June 2011. Retrieved 17 September 2012.
  12. ^ "History of MySQL". MySQL 5.1 Reference Manual. MySQL AB. Retrieved 26 August 2011.
  13. ^ "Sun Microsystems Announces Completion of MySQL Acquisition; Paves Way for Secure, Open Source Platform to Power the Network Economy" (Press release). Sun Microsystems. 26 February 2008. Archived from the original on 28 February 2008. Retrieved 17 September 2012.
  14. ^ "Wikimedia servers — System architecture". Wikimedia Meta-Wiki. Wikimedia Foundation. Retrieved 17 September 2012.
  15. ^ Urlocker, M. Zack (13 December 2005). "Google Runs MySQL". The Open Force. M. Zack Urlocker. Retrieved 3 August 2010. AdWords was built using the MySQL database
  16. ^ Claburn, Thomas (24 April 2007). "Google Releases Improved MySQL Code". InformationWeek. InformationWeek. Retrieved 30 November 2008.
  17. ^ Callaghan, Mark (13 April 2010). MySQL at Facebook. YouTube. Google. Retrieved 3 August 2010. x,000 servers, ... Master-slave replication, InnoDB
  18. ^ Sobel, Jason (21 December 2007). "Keeping Up". The Facebook Blog. Facebook. Retrieved 30 October 2008.
  19. ^ Malik, Om (25 April 2008). "Facebook's Insatiable Hunger for Hardware". GigaOM. GigaOmniMedia. Retrieved 30 October 2008.
  20. ^ Cole, Jeremy (14 April 2011). Big and Small Data at @Twitter. YouTube. Google. Retrieved 20 October 2011.
  21. ^ "MySQL Customer: Flickr". MySQL Customers. Oracle. Retrieved 17 September 2012.
  22. ^ "MySQL Customer: YouTube". MySQL Customers. Oracle. Retrieved 17 September 2012.
  23. ^ a b mysql — The MySQL Command-Line Tool, MySQL Reference Manual
  24. ^ a b mysqladmin – the MySQL command-line tool, MySQL Reference Manual
  25. ^ MySQL Client Programs, MySQL Reference Manual
  26. ^ MySQL Tools Family, SQLMaestro Group
  27. ^ MySQL GUI Tools, WebYog
  28. ^ HeidiSQL, HeidiSQL MySQL GUI
  29. ^ MySQL Workbench, MySQL Downloads
  30. ^ "HeidiSQL Grid editing features".
  31. ^ "LibreOffice Base". Retrieved 5 January 2012.
  32. ^ Home. "Percona Toolkit for MySQL". Percona. Retrieved 26 March 2014.
  33. ^ "MySQL for OpenVMS". vmsmysql.org. 30 March 2011. Retrieved 16 January 2014.
  34. ^ "MySQL Internals Manual". Dev.mysql.com. 4 March 2009. Retrieved 8 June 2009.
  35. ^ "Which Should I Use: MySQL Enterprise or MySQL Community Server?". MySQL AB. Retrieved 8 April 2009.
  36. ^ Guy Harrison; Steven Feuerstein (2008). MySQL Stored Procedure Programming. O'Reilly Media. p. 49. ISBN 978-0-596-10089-6.
  37. ^ "Replication". MySQL.
  38. ^ "MySQL Cluster Replication: Multi-Master and Circular Replication". MySQL.
  39. ^ "MySQL University: MySQL Galera Multi-Master Replication". Oracle Corporation. 9 February 2010.
  40. ^ "MySQL :: InnoDB 1.1 for MySQL 5.5 User's Guide :: C InnoDB Glossary :: ACID". Retrieved 5 January 2011.
  41. ^ "The DB2 for i (IBMDB2I) Storage Engine for MySQL on IBM i". MySQL. Retrieved 18 January 2010.
  42. ^ "Group commit in PostgreSQL". Retrieved 8 April 2012.
  43. ^ "dev.mysql.com". dev.mysql.com. Retrieved 1 February 2012.
  44. ^ a b "dev.mysql.com". dev.mysql.com. Retrieved 1 February 2012.
  45. ^ "MySQL Innodb ZFS Best Practices". Blogs.oracle.com. Retrieved 16 April 2013.
  46. ^ 11 September 2012 (11 September 2012). "Intel SSD 910 vs HDD RAID in tpcc-mysql benchmark". Mysqlperformanceblog.com. Retrieved 16 April 2013.{{cite web}}: CS1 maint: numeric names: authors list (link)
  47. ^ Matsunobu, Yoshinori. "SSD Deployment Strategies for MySQL." Sun Microsystems, 15 April 2010.
  48. ^ "aj_blk: Year 2038 Bug". Ajoeblk.blogspot.in. Retrieved 12 March 2013.
  49. ^ "The future of replication in MySQL". Facebook. Retrieved 9 December 2009.
  50. ^ "Database Sharding". Code Futures. Retrieved 9 December 2009.
  51. ^ "XtraBackup". Percona. Retrieved 19 January 2013.
  52. ^ Mats Kindahl (21 September 2013). "A Brief Introduction to MySQL Fabric". mysqlmusings.blogspot.com. Retrieved 12 December 2013.
  53. ^ Mats Kindahl (27 May 2014). "MySQL Fabric: Musings on Release 1.4.3". mysqlmusings.blogspot.com. Retrieved 18 June 2014.
  54. ^ "Running MySQL on Amazon EC2 with EBS (Elastic Block Store)". Amazon Web Services. Retrieved 5 February 2013.
  55. ^ Finley, Klint. "7 Cloud-Based Database Services". ReadWriteWeb. Retrieved 9 November 2011. {{cite web}}: External link in |work= (help)
  56. ^ "MySQL Server Support at Rackspace". Rackspace.com. Retrieved 10 November 2011.
  57. ^ "Managed Hosting – Terremark". Terremark.com.
  58. ^ "Oracle :: MySQL Open Source License". Mysql.com. Retrieved 8 June 2009.
  59. ^ "MySQL GOES GPL". Archived from the original on 12 August 2001.
  60. ^ "Oracle :: FLOSS License Exception". Mysql.com. Retrieved 8 June 2009.
  61. ^ "Oracle :: MySQL Commercial License". Mysql.com. Retrieved 8 June 2009.
  62. ^ MySQL Support Manual, MySQL Developers
  63. ^ Review of MySQL Server 5.0, Techworld.com, November 2005
  64. ^ MySQL Server Review, LinuxMint.com
  65. ^ Morgan Tocker (13 August 2009). "XtraDB: The Top 10 enhancements". mysqlperformanceblog.com. Retrieved 16 December 2013.
  66. ^ Vadim Tkachenko (21 December 2010). "MySQL 5.5.8 and Percona Server on Fast Flash card (Virident tachIOn)". mysqlperformanceblog.com. Retrieved 16 December 2013.
  67. ^ http://webscalesql.org/faq.html
  68. ^ Basil, Tom (4 September 2001). "Eyewitness account: "Monty Widenius, International Fugitive"". MySQL Life (Mailing list). Retrieved 16 September 2012. {{cite mailing list}}: Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  69. ^ "FAQ on MySQL vs. NuSphere Dispute". MySQL AB. 13 July 2001. Archived from the original on 17 July 2001. Retrieved 16 September 2012.
  70. ^ "Affidavit of Eben Moglen on Progress Software vs. MySQL AB Preliminary Injunction Hearing". Archived from the original on 7 February 2005.
  71. ^ Progress Software Corporation v. MySQL AB, 195 F. Supp. 2d 328 (D. Mass. 2002).
  72. ^ "Judge Saris defers GNU GPL Questions for Trial in MySQL vs. Progress Software" (Press release). Free Software Foundation. 1 March 2002. Retrieved 16 September 2012.
  73. ^ "Oracle Announces the Acquisition of Open Source Software Company, Innobase" (Press release). Oracle. 7 October 2005. Archived from the original on 20 July 2011. Retrieved 16 September 2012. {{cite press release}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  74. ^ "MySQL to Promote New Open Source DB Engines from its Partners and Dev Community" (Press release). MySQL AB. 26 April 2006. Archived from the original on 23 June 2011. Retrieved 16 September 2012.
  75. ^ Babcock, Charles (14 February 2006). "Oracle Buys Sleepycat, Is JBoss Next?". InformationWeek. CPM Media. Retrieved 16 September 2012.
  76. ^ "Changes in MySQL 5.1.12". MySQL 5.1 Reference Manual. MySQL AB. 24 October 2006. Retrieved 16 September 2012.
  77. ^ "Sun Microsystems Announces Agreement to Acquire MySQL, Developer of the World's Most Popular Open Source Database" (Press release). MySQL AB. 16 January 2008. Archived from the original on 18 July 2011. Retrieved 16 September 2012. {{cite press release}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  78. ^ "Oracle to Buy Sun" (Press release). Sun Microsystems. 20 April 2009. Archived from the original on 22 April 2009. Retrieved 16 September 2012.
  79. ^ Thomasch, Paul; Finkle, Jim (20 August 2009). "Oracle wins U.S. approval to buy Sun Microsystems". Reuters. Retrieved 16 September 2012.
  80. ^ Whitney, Lance (14 December 2009). "Oracle pledges to play well with MySQL". CNET. CBS Interactive. Retrieved 16 September 2012.
  81. ^ Michael, Widenius (12 December 2009). "Help saving MySQL". Monty Says. Google. Retrieved 16 September 2012.
  82. ^ Kanaracus, Chris (30 August 2011). "Wikileaks Cable Offers New Insights Into Oracle-Sun Deal". PC World. IDG. Retrieved 16 September 2012.
  83. ^ "Mergers: Commission clears Oracle's proposed acquisition of Sun Microsystems" (Press release). European Union. 21 January 2010. Retrieved 16 September 2012.
  84. ^ "MariaDB versus MySQL – Compatibility". AskMonty Knowledgebase. Monty Program. 30 July 2010. Retrieved 16 September 2012.
  85. ^ Williams, Alex (18 August 2012). "Oracle Makes More Moves To Kill Open Source MySQL". TechCrunch. AOL. Retrieved 16 October 2012.
  86. ^ Smith, Stewart (16 August 2012). "Where to get a BZR tree of the latest MySQL releases". MySQL Performance Blog. Percona. Retrieved 16 October 2012.
  87. ^ Clarke, Gavin (29 November 2012). "Monty on broken MySQL promises: Oracle's going to fork it up". Theregister.co.uk. Retrieved 16 April 2013.
  88. ^ [1]
  89. ^ [2]
  90. ^ http://www.theregister.co.uk/2013/09/12/google_mariadb_mysql_migration/
  91. ^ [3]
  92. ^ [4]
  93. ^ [5]
  94. ^ [6]
  95. ^ [7]
  96. ^ Distributions Which Include MariaDB
  97. ^ Monty has last laugh as distros abandon MySQL
  98. ^ MariaDB living in interesting times
  99. ^ "Five Questions With Michael Widenius – Founder And Original Developer of MySQL". www.opensourcereleasefeed.com. Archived from the original on 13 March 2009. Retrieved 13 October 2012.
  100. ^ "MySQL 3.23 Declared Stable". Archived from the original on 15 August 2001.
  101. ^ "Capttofu: FederatedX Pluggable Storage Engine Released!". Capttofu.livejournal.com. Retrieved 3 April 2009.
  102. ^ "Oreillynet.com". Oreillynet.com. 9 October 2008. Retrieved 1 February 2012.
  103. ^ "Sun Picks Up MySQL For $1 Billion; Open Source Is A Legitimate Business Model". Retrieved 13 October 2012.
  104. ^ "Archives – Oops, we did it again (MySQL 5.1 released as GA with crashing bugs)". Planet MySQL. 29 November 2008. Retrieved 5 February 2013.
  105. ^ "TPC-H Run on MySQL 5.1 and 6.0 | MySQL Performance Blog". MySQL Performance Blog. Retrieved 8 June 2009.
  106. ^ "Oracle.com". Oracle.com. 7 September 2010. Retrieved 1 February 2012.
  107. ^ "dev.mysql.com". dev.mysql.com. Retrieved 1 February 2012.
  108. ^ "dev.mysql.com". dev.mysql.com. Retrieved 1 February 2012.
  109. ^ "MySQL Lists: packagers: MySQL 6.0.11 Alpha has been released!". Lists.mysql.com. Retrieved 1 February 2012.
  110. ^ "What's New in MySQL 5.6". MySQL Developer Zone. Retrieved 21 April 2011.
  111. ^ "The MySQL 5.7.3 Milestone Release is available". MySQL Server Team. Retrieved 13 March 2014.
  112. ^ "B.3. Changes in Release 3.23.x (Lifecycle Support Ended)". Oracle. Retrieved 24 August 2010.
  113. ^ "B.2. Changes in Release 4.0.x (Lifecycle Support Ended)". Oracle. Retrieved 24 August 2010.
  114. ^ "B.1. Changes in Release 4.1.x (Lifecycle Support Ended)". Oracle. Retrieved 24 August 2010.
  115. ^ "C.1. Changes in Release 5.0.x (Lifecycle Support Ended)". Oracle. Retrieved 24 August 2010.
  116. ^ "MySQL 5.1 Release Notes". Oracle. Retrieved 29 January 2014.
  117. ^ "MySQL 5.5 Release Notes". Oracle. Retrieved 29 January 2014.
  118. ^ "MySQL 5.6 Release Notes". Oracle. Retrieved 29 January 2014.
  119. ^ "MySQL 5.7 Release Notes". Oracle. Retrieved 13 March 2014.
Wikimedia Commons has media related to MySQL.
Wikibooks has more on the topic of: MySQL

Retrieved from "https://en.wikipedia.org/w/index.php?title=MySQL&oldid=613637580"