Jump to content

MySQL

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by ChamithN (talk | contribs) at 08:08, 12 October 2018 (Reverted good faith edits by Chilevipul (talk): Unnecessary. (TW)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Original author(s)MySQL AB
Developer(s)Oracle Corporation
Initial release23 May 1995; 29 years ago (1995-05-23)
Stable release
8.0.12[1] / 27 July 2018; 6 years ago (2018-07-27)
Repository
Written inC, C++[2]
Operating systemLinux, Solaris, macOS, Windows, FreeBSD[3]
Available inEnglish
TypeRDBMS
LicenseGPL (version 2) or proprietary[4]
WebsiteMySQL.com

MySQL (/ˌmaɪˌɛsˌkjuːˈɛl/ "My S-Q-L")[5] is an open-source relational database management system (RDBMS).[6] Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,[7] and "SQL", the abbreviation for Structured Query Language. 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.[8] For proprietary use, several paid editions are available, and offer additional functionality.

MySQL is a central component of the LAMP open-source web application software stack (and other "AMP" stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python". Applications that use the MySQL database include: TYPO3, MODx, Joomla, WordPress, Simple Machines Forum, phpBB, MyBB, and Drupal. MySQL is also used in many high-profile, large-scale websites, including Google[9][10] (though not for searches), Facebook,[11][12][13] Twitter,[14] Flickr,[15] and YouTube.[16]

Overview

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, eComStation, i5/OS, 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,[19] beginning from 28 June 2000[20] (which in 2009 has been extended with a FLOSS License Exception)[21] or to use a proprietary license.[22]

Support can be obtained from the official manual.[23] 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 MariaDB 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".[24] It has also been tested to be a "fast, stable and true multi-user, multi-threaded sql database server".[25]

History

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994.[26] 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.[citation needed][dubious – discuss]

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[27]
  • 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",[28] 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".[29]
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).[31]
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.[32]
  • Oracle acquired Sun Microsystems on 27 January 2010.[33][34][35]
  • The day Oracle announced the purchase of Sun, Michael "Monty" Widenius forked MySQL, launching MariaDB, and took a swath of MySQL developers with him.[36]
  • MySQL Server 5.5 was 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[37]
    • Improved SMP support[38]
    • 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[39] 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.[40] 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.[41] 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.[42] As of MySQL 5.7.8, August 2015,[43] MySQL supports a native JSON data type defined by RFC 7159.[44]
  • MySQL Server 8.0 was announced in April 2018,[45] 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.[46]

Release history

Release General availability Latest minor version Latest release End of support[47]
Old version, no longer maintained: 5.1 November 14, 2008; 16 years ago (2008-11-14)[48] 5.1.73[49] 2013-12-03 December 2013
Old version, yet still maintained: 5.5 December 3, 2010; 13 years ago (2010-12-03)[50] 5.5.61 2018-07-27 December 2018
Old version, yet still maintained: 5.6 February 5, 2013; 11 years ago (2013-02-05)[51] 5.6.41 2018-07-27 February 2021
Old version, yet still maintained: 5.7 October 21, 2015; 9 years ago (2015-10-21) [52] 5.7.23 2018-07-27 October 2023
Current stable version: 8.0 April 19, 2018; 6 years ago (2018-04-19) [53] 8.0.12[54] 2018-07-27 April 2026
Legend:
Old version, not maintained
Old version, still maintained
Latest version
Latest preview version
Future release

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.[55]

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".[56][57]

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.[58] After a preliminary hearing before Judge Patti Saris on 27 February 2002, the parties entered settlement talks and eventually settled.[59] After the hearing, FSF commented that "Judge Saris made clear that she sees the GNU GPL to be an enforceable and binding license."[60]

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.[61] 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.[62]

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

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

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

A movement against Oracle's acquisition of MySQL, to "Save MySQL"[69] 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, 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.[70][71][72] 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, as revealed by WikiLeaks, the US Department of Justice, at the request of Oracle, pressured the EU to approve the merger unconditionally.[73] The European Commission eventually unconditionally approved Oracle's acquisition of MySQL on 21 January 2010.[74]

In January 2010, before 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.5 and aims to maintain compatibility with Oracle-provided versions.[75]

Features

MySQL is offered under two different editions: the open source MySQL Community Server and the proprietary Enterprise Server.[76] 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[77]
  • 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.[78]
  • 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[79]
  • SSL support
  • Query caching
  • Sub-SELECTs (i.e. nested SELECTs)
  • Built-in replication support (i.e., master-master replication and master-slave replication) with one master per slave, many slaves per master.[80] Multi-master replication is provided in MySQL Cluster,[81] and multi-master support can be added to unclustered configurations using Galera Cluster.[82]
  • Full-text indexing and searching[a]
  • Embedded database library
  • Unicode support[b]
  • 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.[83] Check constraints are parsed but ignored by all storage engines.[84][85]

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

MySQL database's inbuilt functions like UNIX_TIMESTAMP() will return 0 after 03:14:07 UTC on 19 January 2038.[87] Recently, there had been an attempt to solve the problem which had been assigned to the internal queue.[88]

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.

LAMP software bundle, displayed here together with Squid.

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.[89] 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.[90]

Backup software

mysqldump is a logical backup tool included with both community and enterprise editions of MySQL. It supports backing up from all storage engines. MySQL Enterprise Backup is a hot backup utility included as part of the MySQL Enterprise subscription from Oracle, offering native InnoDB hot backup, as well as backup for other storage engines.

XtraBackup is an open-source MySQL hot backup software program. 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.[91]

High availability software

MySQL Fabric is 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 supports procedure execution 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.[92]

Cloud deployment

Main article: Cloud database

MySQL can also be run on cloud computing platforms such as Microsoft Azure, Amazon EC2, 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.[93]
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.[94] Notable cloud-based MySQL services are the Amazon Relational Database Service; Oracle MySQL Cloud Service, Azure Database for MySQL, Rackspace; HP Converged Cloud; Heroku and Jelastic. (Note In this model the database service provider takes responsibility for maintaining the host and database)

User interfaces

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. GUIs are easier to learn than command-line interfaces (CLIs), which require commands to be typed on the keyboard.

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 are:

MySQL Workbench running on macOS
MySQL Workbench
MySQL Workbench is the official 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 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.
Adminer
Adminer (formerly known as phpMinAdmin) is a free MySQL front end for managing content in MySQL databases (since version 2, it also works on PostgreSQL, MS SQL, SQLite and Oracle SQL databases). Adminer is distributed under the Apache license (or GPL v2) in the form of a single PHP file (around 300 KiB in size), and is capable of managing multiple databases, with many CSS skins available. Its author is Jakub Vrána who started to develop this tool as a light-weight alternative to phpMyAdmin, in July 2007.
ClusterControl
ClusterControl is an end-to-end MySQL management system GUI that provides the ability to deploy, monitor, manage and scale MySQL instances from a single interface. It is developed by Severalnines.
The Community version of ClusterControl is free to use and let's the user deploy and monitor their MySQL instances. Advanced features like load balancing, backup & restore, failover, etc are part of a paid offering.
Database Workbench
Database Workbench is a software application for development and administration of multiple relational databases using SQL, with interoperationality between different database systems, developed by Upscene Productions.
Because Databases Workbench supports multiple database systems, it can provide software developers with the same interface and development environment for these otherwise different database systems and also includes cross database tools.
Database Workbench supports the following relational databases: Oracle Database, Microsoft SQL Server, SQL Anywhere, Firebird, NexusDB, InterBase, MySQL and MariaDB. Database Workbench 5 runs on 32-bit or 64 bit Windows platforms. Under Linux, FreeBSD or macOS Database Workbench can operate using Wine.
DBeaver
DBeaver is an SQL client and a database administration tool. DBeaver includes extended support of following databases: MySQL and MariaDB, PostgreSQL, Oracle, DB2 (LUW), EXASOL, SQL Server, Sybase, Firebird, Teradata, Vertica, Apache Phoenix, Netezza, Informix, Apache Derby, Apache Phoenix, H2, SQLite and any other database which has JDBC or ODBC driver. DBeaver is free and open source software that is distributed under the Apache License 2.0. The source code is hosted on GitHub.
DBEdit
DBEdit is a database editor, which can connect to an Oracle, DB2, MySQL and any database that provides a JDBC driver. It runs on Windows, Linux and Solaris. DBEdit is free and open source software and distributed under the GNU General Public License. The source code is hosted on SourceForge.
HeidiSQL
HeidiSQL, previously known as MySQL-Front, is a free and open source client, or frontend for MySQL (and for its forks like MariaDB and Percona Server), Microsoft SQL Server and PostgreSQL. HeidiSQL is developed by German programmer Ansgar Becker and a few other contributors in Delphi. To manage databases with HeidiSQL, users must login to a local or remote MySQL server with acceptable credentials, creating a session. Within this session users may manage MySQL Databases within the connected MySQL server, disconnecting from the server when done. Its feature set is sufficient for most common and advanced database, table and data record operations but remains in active development to move towards the full functionality expected in a MySQL Frontend.
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[95]
Navicat
Navicat is a series of graphical database management and development software produced by PremiumSoft CyberTech Ltd. for MySQL, MariaDB, Oracle, SQLite, PostgreSQL and Microsoft SQL Server. It has an Explorer-like graphical user interface and supports multiple database connections for local and remote databases. Its design is made to meet the needs of a variety of audiences, from database administrators and programmers to various businesses/companies that serve clients and share information with partners.
Navicat is a cross-platform tool and works on Microsoft Windows, OS X and Linux platforms. Upon purchase, users are able to select a language for the software from eight available languages: English, French, German, Spanish, Japanese, Polish, Simplified Chinese and Traditional Chinese.
OpenOffice.org
OpenOffice.org Base is freely available and can manage MySQL databases if the entire suite is installed.
phpMyAdmin
phpMyAdmin is a free and open source tool written in PHP intended to handle the administration of MySQL with the use of a web browser. It can perform various tasks such as creating, modifying or deleting databases, tables, fields or rows; executing SQL statements; or managing users and permissions. The software, which is available in 78 languages,[96] is maintained by The phpMyAdmin Project.[97]
It can import data from CSV and SQL, and transform stored data into any format using a set of predefined functions, like displaying BLOB-data as images or download-links.
Sequel Pro
Sequel Pro is a free and open-source MacOS application for working with MySQL databases locally or remotely. It uses the freemium model, where the Gratis users are actually getting features to most of the basic services. It takes a SQL Table itself to manage these requests. It can handle the new "fun" UTF-8 features for newer unicode as well as having multiple GB tables without issue Sourceforge[98] is its home.
SQLBuddy
SQLBuddy is an open-source web-based application written in PHP intended to handle the administration of MySQL and SQLite with the use of a Web browser. The project places an emphasis on ease of installation and a simple user interface.
SQLyog
SQLyog is a GUI tool available in free as well as paid versions. Data manipulations (e.g., insert, update, and delete) may be done from a spreadsheet-like interface. Its editor has syntax highlighting and various automatic formatting options. Both raw table data and a result set from a query can be manipulated. Its data search feature uses Google-like search syntax and translates to SQL transparently for the user. It has a backup tool for performing unattended backups. Backups may be compressed and optionally stored as a file-per-table as well as identified with a timestamp.
Toad for MySQL
Toad for MySQL is a software application from Dell Software that database developers, database administrators and data analysts use to manage both relational and non-relational databases using SQL. Toad supports many databases and environments. It runs on all 32-bit/64-bit Windows platforms, including Microsoft Windows Server, Windows XP, Windows Vista, Windows 7 and 8 (32-Bit or 64-Bit). Dell Software has also released a Toad Mac Edition. Dell provides Toad in commercial and trial/freeware versions. The freeware version is available from the ToadWorld.com community.
Webmin
Webmin is a web-based system configuration tool for Unix-like systems, although recent versions can also be installed and run on Windows. With it, it is possible to configure operating system internals, such as users, disk quotas, services or configuration files, as well as modify and control open source apps, such as the Apache HTTP Server, PHP or MySQL.
Webmin is largely based on Perl, running as its own process and web server. It defaults to TCP port 10000 for communicating, and can be configured to use SSL if OpenSSL is installed with additional required Perl Modules.
It is built around modules, which have an interface to the configuration files and the Webmin server. This makes it easy to add new functionality. Due to Webmin's modular design, it is possible for anyone who is interested to write plugins for desktop configuration.
Webmin also allows for controlling many machines through a single interface, or seamless login on other webmin hosts on the same subnet or LAN.

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.[99][100]

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.[101] 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.

Application programming interfaces

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 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.

Project forks

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. Being a fork of a leading open source software system, it is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.[36] Contributors are required to share their copyright with the MariaDB Foundation.[102] MariaDB intends to maintain high compatibility with MySQL, ensuring a "drop-in" replacement capability with library binary equivalency and exact matching with MySQL APIs and commands.[103] There are some documented differences and incompatibilities between versions of MySQL and MariaDB,[103] however, and some tools for interacting with MySQL, such as the MySQL Workbench, are not fully compatible with MariaDB.[104] It includes the XtraDB storage engine for replacing InnoDB,[105] as well as a new storage engine, Aria, that intends to be both a transactional and non-transactional engine perhaps even included in future versions of MySQL.[106]
Percona Server
Percona Server, forked by Percona, aims to retain close compatibility to the official MySQL releases, while focusing on performance and increased visibility into server operations.[107] Also included in Percona Server is XtraDB, Percona's fork of the InnoDB Storage Engine. Percona freely includes a number of scalability, availability, security and backup features only available in MySQL's commercial Enterprise edition.[108]

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.[109] 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.[110][111] The project's source code is licensed under version 2 of the GNU General Public License, and is hosted on GitHub.[112][113]

See also

Notes

  1. ^ Initially, it was a MyISAM-only feature; supported by InnoDB since the release of MySQL 5.6.
  2. ^ Prior to MySQL 5.5.3, UTF-8 and UCS-2 encoded strings are limited to the BMP; MySQL 5.5.3 and later use utf8mb4 for full unicode support.
  3. ^ In MySQL 5.0, storage engines must be compiled in; since MySQL 5.1, storage engines can be dynamically loaded at run time.

References

  1. ^ "MySQL 8.0 Release Notes". mysql.com. Retrieved 31 July 2018.
  2. ^ "MySQL: Project Summary". Ohloh. Black Duck Software. Retrieved 17 September 2012.
  3. ^ "Supported Platforms: MySQL Database". Oracle. Retrieved 24 March 2014.
  4. ^ "Downloads". MySQL. Retrieved 3 August 2014.
  5. ^ "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")
  6. ^ "DB-Engines Ranking". Retrieved 12 February 2015.
  7. ^ "History of MySQL". MySQL 5.1 Reference Manual. MySQL AB. Retrieved 26 August 2011.
  8. ^ "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.
  9. ^ 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
  10. ^ Claburn, Thomas (24 April 2007). "Google Releases Improved MySQL Code". InformationWeek. InformationWeek. Retrieved 30 November 2008.
  11. ^ Callaghan, Mark (13 April 2010). MySQL at Facebook. YouTube. Google. Retrieved 3 August 2010. x,000 servers, ... Master-slave replication, InnoDB
  12. ^ Sobel, Jason (21 December 2007). "Keeping Up". The Facebook Blog. Facebook. Retrieved 30 October 2008.
  13. ^ Malik, Om (25 April 2008). "Facebook's Insatiable Hunger for Hardware". GigaOM. GigaOmniMedia. Retrieved 30 October 2008.
  14. ^ Cole, Jeremy (14 April 2011). Big and Small Data at @Twitter. YouTube. Google. Retrieved 20 October 2011.
  15. ^ "MySQL Customer: Flickr". MySQL Customers. Oracle. Retrieved 17 September 2012.
  16. ^ "MySQL Customer: YouTube". MySQL Customers. Oracle. Retrieved 17 September 2012.
  17. ^ "MySQL Internals Manual". Dev.mysql.com. 4 March 2009. Retrieved 8 June 2009.
  18. ^ "MySQL for OpenVMS". vmsmysql.org. 30 March 2011. Retrieved 16 January 2014.
  19. ^ "Oracle :: MySQL Open Source License". Mysql.com. Retrieved 8 June 2009.
  20. ^ "MySQL GOES GPL". Archived from the original on 12 August 2001.
  21. ^ "Oracle :: FLOSS License Exception". Mysql.com. Retrieved 8 June 2009.
  22. ^ "Oracle :: MySQL Commercial License". Mysql.com. Retrieved 8 June 2009.
  23. ^ MySQL Support Manual, MySQL Developers
  24. ^ Review of MySQL Server 5.0, Techworld.com, November 2005
  25. ^ MySQL Server Review, LinuxMint.com
  26. ^ "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.
  27. ^ "MySQL 3.23 Declared Stable". Archived from the original on 15 August 2001.
  28. ^ "Capttofu: FederatedX Pluggable Storage Engine Released!". Capttofu.livejournal.com. Archived from the original on 13 August 2011. Retrieved 3 April 2009. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  29. ^ "MySQL Federated Tables: The Missing Manual". O’Reilly Media. 8 October 2006. Retrieved 1 February 2012.
  30. ^ "Sun Picks Up MySQL For $1 Billion; Open Source Is A Legitimate Business Model". Retrieved 13 October 2012.
  31. ^ "Archives – Oops, we did it again (MySQL 5.1 released as GA with crashing bugs)". Planet MySQL. 29 November 2008. Archived from the original on 30 December 2008. Retrieved 5 February 2013. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  32. ^ "TPC-H Run on MySQL 5.1 and 6.0 | MySQL Performance Blog". MySQL Performance Blog. Retrieved 8 June 2009.
  33. ^ "Oracle Completes Acquisition of Sun" (Press release). Oracle. 27 January 2010. Retrieved 1 February 2012.
  34. ^ "Overview and Frequently Asked Questions" (PDF).
  35. ^ "Oracle's ambitious plans for integrating Sun's technology". InfoWorld. 27 January 2010.
  36. ^ a b "Dead database walking: MySQL's creator on why the future belongs to MariaDB". Computerworld. 28 March 2013. Retrieved 11 September 2013.
  37. ^ "InnoDB I/O Subsystem Changes". dev.mysql.com. Archived from the original on 10 February 2012. Retrieved 1 February 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  38. ^ "Scalability Improvements". dev.mysql.com. Archived from the original on 10 February 2012. Retrieved 1 February 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  39. ^ "MySQL Lists: packagers: MySQL 6.0.11 Alpha has been released!". Lists.mysql.com. Retrieved 1 February 2012.
  40. ^ http://www.oracle.com/us/corporate/press/1904335
  41. ^ "What's New in MySQL 5.6". MySQL Developer Zone. Archived from the original on 23 April 2011. Retrieved 21 April 2011. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  42. ^ "Oracle Announces General Availability of MySQL 5.7". Oracle. Retrieved 1 November 2015.
  43. ^ https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-8.html#mysqld-5-7-8-json
  44. ^ https://dev.mysql.com/doc/refman/5.7/en/json.html
  45. ^ https://blogs.oracle.com/mysql/announcing-general-availability-of-mysql-80
  46. ^ "8.0.0-dmr (Milestone Release)". Retrieved 12 September 2016.
  47. ^ Oracle Lifetime Support Policy
  48. ^ "A.1 MySQL 5.1 FAQ: General". docs.oracle.com. Retrieved 2 August 2017.
  49. ^ "MySQL 5.1 Release Notes". docs.oracle.com. Retrieved 2 August 2017.
  50. ^ "MySQL: MySQL 5.5 Release Notes". dev.mysql.com. Retrieved 15 January 2018.
  51. ^ "MySQL: MySQL 5.6 Release Notes". dev.mysql.com. Retrieved 15 January 2018.
  52. ^ "MySQL: MySQL 5.7 Release Notes". dev.mysql.com. Retrieved 15 January 2018.
  53. ^ "Mysql: Mysql 8.0 Release".
  54. ^ "MySQL: MySQL 8.0 Release Notes". dev.mysql.com. Retrieved 25 September 2017.
  55. ^ "MySQL 8 is coming". opensource.com. Retrieved 27 April 2018.
  56. ^ Basil, Tom (4 September 2001). "Eyewitness account: "Monty Widenius, International Fugitive"". MySQL Life (Mailing list). Archived from the original on 4 October 2013. Retrieved 16 September 2012. {{cite mailing list}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help); Unknown parameter |mailinglist= ignored (|mailing-list= suggested) (help)
  57. ^ "FAQ on MySQL vs. NuSphere Dispute". MySQL AB. 13 July 2001. Archived from the original on 17 July 2001. Retrieved 16 September 2012.
  58. ^ "Affidavit of Eben Moglen on Progress Software vs. MySQL AB Preliminary Injunction Hearing". Archived from the original on 7 February 2005.
  59. ^ Progress Software Corporation v. MySQL AB, 195 F. Supp. 2d 328 (D. Mass. 2002).
  60. ^ "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.
  61. ^ "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)
  62. ^ "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. {{cite press release}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  63. ^ Babcock, Charles (14 February 2006). "Oracle Buys Sleepycat, Is JBoss Next?". InformationWeek. CPM Media. Retrieved 16 September 2012.
  64. ^ "Changes in MySQL 5.1.12". MySQL 5.1 Reference Manual. MySQL AB. 24 October 2006. Archived from the original on 20 October 2012. Retrieved 16 September 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  65. ^ "Sun Microsystems Announces Agreement to Acquire MySQL, Developer of the World's Most Popular Open Source Database" (Press release). Sun Microsystems. 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)
  66. ^ "Oracle to Buy Sun" (Press release). Sun Microsystems. 20 April 2009. Archived from the original on 22 April 2009. Retrieved 16 September 2012. {{cite press release}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  67. ^ Thomasch, Paul; Finkle, Jim (20 August 2009). "Oracle wins U.S. approval to buy Sun Microsystems". Reuters. Retrieved 16 September 2012.[permanent dead link‍]
  68. ^ Whitney, Lance (14 December 2009). "Oracle pledges to play well with MySQL". CNET. Retrieved 16 September 2012.
  69. ^ Michael, Widenius (12 December 2009). "Help saving MySQL". Monty Says. Google. Retrieved 16 September 2012.
  70. ^ "The Software Freedom Law Center Submits an Opinion on the Oracle/Sun Merger to the EC". www.softwarefreedom.org. Software Freedom Law Center. 4 December 2009. Retrieved 1 February 2018.
  71. ^ Lai, Eric (28 October 2009). "Many open-sourcers back an Oracle takeover of MySQL". www.infoworld.com. InfoWorld. Retrieved 1 February 2018.
  72. ^ Wildeboer, Jan (5 January 2010). "Why I will not sign the MySQL petition". jan.wildeboer.net. Retrieved 1 February 2018.
  73. ^ Kanaracus, Chris (30 August 2011). "Wikileaks Cable Offers New Insights Into Oracle-Sun Deal". PC World. Retrieved 16 September 2012.
  74. ^ "Mergers: Commission clears Oracle's proposed acquisition of Sun Microsystems" (Press release). European Union. 21 January 2010. Retrieved 16 September 2012.
  75. ^ "MariaDB versus MySQL – Compatibility". AskMonty Knowledgebase. Monty Program. 30 July 2010. Archived from the original on 27 July 2010. Retrieved 16 September 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  76. ^ "Which Should I Use: MySQL Enterprise or MySQL Community Server?". MySQL AB. Archived from the original on 9 April 2009. Retrieved 8 April 2009. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  77. ^ Guy Harrison; Steven Feuerstein (2008). MySQL Stored Procedure Programming. O'Reilly Media. p. 49. ISBN 978-0-596-10089-6.
  78. ^ "Monitoring RDS MySQL performance metrics". Datadog. 20 October 2015. Retrieved 14 December 2015.
  79. ^ "MySQL :: InnoDB 1.1 for MySQL 5.5 User's Guide :: C InnoDB Glossary :: ACID". Archived from the original on 25 December 2010. Retrieved 5 January 2011. {{cite web}}: Unknown parameter |dead-url= ignored (|url-status= suggested) (help)
  80. ^ "Replication". MySQL.
  81. ^ "MySQL Cluster Replication: Multi-Master and Circular Replication". MySQL.
  82. ^ "MySQL University: MySQL Galera Multi-Master Replication". Oracle Corporation. 9 February 2010.
  83. ^ "InnoDB and FOREIGN KEY Constraints". MySQL. Retrieved 11 April 2015.
  84. ^ "Bug #3464 Constraints: support CHECK". MySQL. 14 April 2004. Retrieved 11 April 2015.
  85. ^ "MySQL 8.0 Reference Manual: CREATE TABLE Syntax". MySQL Reference Manual. Oracle. Retrieved 7 May 2018. {{cite web}}: Cite has empty unknown parameter: |dead-url= (help)
  86. ^ a b "CREATE TRIGGER Syntax". MySQL. Retrieved 11 April 2015.
  87. ^ "MySQL Bugs: #12654: 64-bit unix timestamp is not supported in MySQL functions". MySQL. 18 August 2005. Retrieved 6 October 2017.
  88. ^ "Allow dates beyond 2038 by dveeden · Pull Request #130 · mysql/mysql-server". GitHub, Inc. 22 March 2017. Retrieved 6 October 2017.
  89. ^ "The future of replication in MySQL". Facebook. Retrieved 9 December 2009.
  90. ^ "Database Sharding". Code Futures. Archived from the original on 16 January 2010. Retrieved 9 December 2009. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  91. ^ "XtraBackup". Percona. Retrieved 19 January 2013.
  92. ^ Mats Kindahl (27 May 2014). "MySQL Fabric: Musings on Release 1.4.3". mysqlmusings.blogspot.com. Retrieved 18 June 2014.
  93. ^ "Running MySQL on Amazon EC2 with EBS (Elastic Block Store)". Amazon Web Services. Retrieved 5 February 2013.
  94. ^ Finley, Klint. "7 Cloud-Based Database Services". ReadWriteWeb. Archived from the original on 9 November 2011. Retrieved 9 November 2011. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  95. ^ "LibreOffice Base". Archived from the original on 7 January 2012. Retrieved 5 January 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  96. ^ "Translations". phpMyAdmin. Retrieved 23 December 2014.
  97. ^ "Team". phpMyAdmin. Retrieved 3 March 2013.
  98. ^ https://sequelpro
  99. ^ mysql — The MySQL Command-Line Tool, MySQL Reference Manual
  100. ^ mysqladmin – the MySQL command-line tool, MySQL Reference Manual
  101. ^ Home. "Percona Toolkit for MySQL". Percona. Retrieved 26 March 2014.
  102. ^ "Contributing Code". MariaDB KnowledgeBase. Retrieved 17 September 2014.
  103. ^ a b "MariaDB versus MySQL - Compatibility". MariaDB KnowledgeBase. Retrieved 16 September 2016.
  104. ^ "Monitoring MySQL performance metrics". Datadog. Retrieved 16 September 2016.
  105. ^ "About XtraDB". MariaDB KnowledgeBase. Retrieved 16 September 2016.
  106. ^ "Aria FAQ". MariaDB KnowledgeBase. Retrieved 16 September 2016.
  107. ^ Percona Server Frequently Asked Questions, How is it related to other MySQL forks?
  108. ^ "Percona challenges Oracle with alternate MySQL release". PC World. Retrieved 12 February 2015.
  109. ^ Clark, Jack (17 March 2011). "MySQL fork Drizzle gets general release". ZDNet. Retrieved 3 January 2016.
  110. ^ Steven J. Vaughan-Nichols (28 March 2013). "WebScaleSQL: MySQL for Facebook-sized databases". ZDNet. Retrieved 1 April 2014.
  111. ^ Klint Finley (27 March 2013). "Google and Facebook Team Up to Modernize Old-School Databases". Wired. Retrieved 1 April 2014.
  112. ^ Jack Clark (27 March 2013). "Forkin' 'L! Facebook, Google and friends create WebScaleSQL from MySQL 5.6". The Register. Retrieved 1 April 2014.
  113. ^ "Frequently Asked Questions". webscalesql.org. 27 March 2014. Retrieved 1 April 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=863674318"