Catalonia is Not Spain



From Wikipedia, the free encyclopedia

(Redirected from My sql)

Jump to: navigation, search

Developer: MySQL AB
Latest release: 5.0.37 (Community Server) / February 27, 2007
Preview release: 5.1.16-beta / February 26, 2007
OS: Cross-platform
License: GPL or Commercial License or Subscription Agreement

MySQL (pronounced /mɑɪ ɛs kjuː ɛl/) is a multithreaded, multi-user SQL database management system (DBMS)[1] which has, according to MySQL AB, more than 10 million installations.[2]

MySQL is owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, which holds the copyright to most of the codebase. This is similar to the JBoss model and how the Free Software Foundation handles copyright in its projects, and dissimilar to how the Apache project does it, where the software is developed by a public community and the copyright to the codebase is owned by its individual authors.

The company develops and maintains the system, selling support and service contracts, as well as proprietary-licensed copies of MySQL, and employing people all over the world who collaborate via the Internet. MySQL AB was founded by David Axmark, Allan Larsson, and Michael “Monty” Widenius. The CEO is Marten Mickos.

The MySQL company also sells another DBMS, MaxDB, which is from an unrelated codebase.




[edit] Programming languages

There are APIs available that allow applications written in numerous programming languages to access MySQL databases, including: C, C++, C#, D, Borland Delphi (via dbExpress), Eiffel, Smalltalk, Java (with a native Java driver implementation), Lisp, Perl, PHP, Python, Ruby, REALbasic (Mac), FreeBasic, and Tcl; each of these uses a specific API. 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. MySQL is mostly implemented in ANSI C.

[edit] Uses

MySQL is popular for web applications and acts as the database component of the LAMP, MAMP, and WAMP platforms (Linux/Mac/Windows-Apache-MySQL-PHP/Perl/Python), and for open-source bug tracking tools like Bugzilla. Its popularity as a web application is closely tied to the popularity of PHP, which is often combined with MySQL and nicknamed the Dynamic Duo. It is easy to find many references that combine the two in websites and books (PHP and MySQL for Dummies, PHP and MySQL Bible, Beginning PHP and MySQL, etc.). PHP and MySQL are also essential components for running the popular WordPress blogging platform. Wikipedia runs on MediaWiki software, which also uses PHP and a MySQL database.

[edit] Documentation & Administration

Information on using MySQL can be found on the company’s site, under their Documentation section. There are also many books on MySQL that have been written.

To administer MySQL databases one can use the included command-line tool (commands: mysql and mysqladmin). Also downloadable from the MySQL site are GUI administration tools: MySQL Administrator and MySQL Query Browser. Both of the GUI tools are now included in one package called MySQL GUI Tools.

A widespread and popular alternative, written in PHP, is the free software web application phpMyAdmin which is a server side tool. For client side MySQL administration and development, the leading tools are Navicat MySQL GUI by PremiumSoft and MySQL admin family by SQL Maestro Group, which provide the same functionality as phpMyAdmin but more advanced in the Import/Export, Query Building, OLAP, BLOB Editing, Backup and Data Sync. features. Navicat is also available for PostgreSQL – Navicat PostgreSQL Manager.

[edit] Program specifications

[edit] Platforms

MySQL works on many different platforms—including AIX, BSDi, FreeBSD, HP-UX, GNU/Linux, Mac OS X, NetBSD, Novell NetWare, OpenBSD, OS/2 Warp, QNX, SGI IRIX, Solaris, SunOS, SCO OpenServer, SCO UnixWare, Tru64, Windows 95, Windows 98, Windows ME, Windows NT, Windows 2000, Windows XP and Windows Vista. A port of MySQL to OpenVMS is also available.[3]

[edit] The latest production version

As of October 2006, MySQL offers MySQL 5.0 in two different variants: the MySQL Community Server and Enterprise Server. Both 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
  • Triggers
  • Cursors
  • Updatable Views
  • True VARCHAR support
  • Strict mode
  • 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, Archive for storing historical data in little space)
  • Transactions with the InnoDB, BDB and Cluster storage engines; savepoints with InnoDB
  • SSL support
  • Query caching
  • Sub-SELECTs (i.e. nested SELECTs)
  • Replication with one master per slave, many slaves per master, no automatic support for multiple masters per slave.
  • Full-text indexing and searching using MyISAM engine
  • Embedded database library
  • Partial Unicode support (UTF-8 sequences longer than 3 bytes are not supported; UCS-2 encoded strings are also limited to the BMP)
  • ACID compliance using the InnoDB, BDB and Cluster engines
  • Shared-nothing clustering through MySQL Cluster

The MySQL Enterprise Server is released once per month, but the binaries are not publicly available from the download pages. The sources can be obtained under the GPL license from MySQL’s FTP server[1] and all patches for bug fixes are immediately available from the public MySQL BitKeeper repositories. The MySQL Community Server is published on an unspecified schedule under the GPL license and contains all bug fixes that were shipped with the last MySQL Enterprise Server release. Binaries are no longer provided for every release of the Community Server.[4][5]

[edit] Future releases

The MySQL 5.1 roadmap outlines support for:

Foreign key support for all storage engines will likely be released with MySQL 5.2 (although it has been present since version 3.23.44 for InnoDB).

The current MySQL 5.1 development release is 5.1.16 beta

A new storage engine is also in the works, called Falcon. A preview of Falcon is available in MySQL 5.2 Alpha.

[edit] Distinguishing features

The following features are implemented by MySQL but not by some other RDBMSes:

  • Multiple storage engines, allowing you to choose the one which 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):
    • Native storage engines (MyISAM, Falcon, Merge, Memory (heap), Federated, Archive, CSV, Blackhole, Cluster)
    • Partner-developed storage engines (InnoDB, solidDB, NitroEDB, BrightHouse)
    • Community-developed storage engines (PrimeBase XT, OpenOLAP)
    • Custom storage engines
  • Commit grouping, gathering multiple transactions from multiple connections together to increase the number of commits per second.

[edit] Server compilation type

There are 3 types of MySQL Server Compilations:

  • Standard: The MySQL-Standard binaries are recommended for most users, and include the InnoDB storage engine.
  • Max: (not MaxDB, which is a cooperation with SAP) is mysqld-max Extended MySQL Server. The MySQL-Max binaries include additional features that may not have been as extensively tested or are not required for general usage.
  • The MySQL-Debug binaries have been compiled with extra debug information, and are not intended for production use, because the included debugging code may cause reduced performance.

Beginning with MySQL 5.1, MySQL AB has stopped providing three different package variants. There will only be one MySQL server package, which includes a mysqld binary with all functionality and storage engines enabled. Instead of providing a separate debug package, a server binary with extended debugging information is also included in the standard package, named mysqld-debug mm.[6]

[edit] Source code specifics

MySQL is written in C and C++. The SQL parser uses yacc and home-brewed lexer. A document describing some of the internal structures of the code and the coding guidelines is available from the MySQL web site[7]

[edit] Support

Via MySQL Network MySQL AB offers support itself, including 24/7 30-minute response time, with the support team having direct access to the developers as necessary to handle problems. In addition it hosts forums and mailing lists and employees and other users are often available in several IRC channels providing assistance.

Members of the MySQL Network enjoy access to binaries and software that is certified for their particular operating system, and the codebase changes much less frequently than the Community Edition of the MySQL Database Server engine. The Network maintains several levels of membership based on importance and urgency for response times.

[edit] Licensing

MySQL AB makes MySQL Server available as free software under the GNU General Public License (GPL), but they also offer the MySQL Enterprise subscription offering for business users and dual-license it under traditional proprietary licensing arrangements for cases where the intended use is incompatible with the GPL.

Both the MySQL server software itself and the client libraries are distributed under a dual-licensing format. Users may choose the GNU General Public License [2], which MySQL has extended with a FLOSS License Exception. It allows Software licensed under other OSI-compliant Open Source licenses, which are not compatible to the GPL, to link against the MySQL client libraries. [3]

Customers that do not wish to be bound to the terms of the GPL may choose to purchase a proprietary license. [4]

Like many open-source programs, the name “MySQL” is trademarked and may only be used with the trademark holder’s permission.

Some users have independently continued to develop earlier versions of the client libraries, which was distributed under the less-restrictive Lesser General Public License. [5]

[edit] Pronunciation

“MySQL” is officially pronounced as “My Ess Queue Ell” /maɪ ɛs kjuː ɛl/, not “My sequel” /maɪ siːkwəl/. However, the company does not take issue with the pronunciation “My sequel” or other local variations.

The “My” portion of the name supposedly comes from the name of Widenius’s child [6], spelled “My” but pronounced in the local language as /my/ (or approximately in English, “me”).

The “SQL” portion uses the fully spelled-out pronunciation of the initials, S-Q-L (Structured Query Language), not the “sequel” pronunciation. This adheres to the official ANSI pronunciation but conflicts with the earlier IBM database of that name. [7]

The Swedish (MySQL AB is a Swedish company) word Myskväll (/myskvæl/ “cozy evening”, or “My’s evening” as Mys kväll) is pronounced in a similar way, but this may be a coincidence. Nevertheless this pronunciation is quite usual in Sweden.

[edit] Criticisms of MySQL

The neutrality of this section is disputed.
Please see the discussion on the talk page.

Early versions of MySQL lacked many standard relational database management system (RDBMS) features, usually with the goal of trading guaranteed accuracy for speed. Many (but not yet all) such criticisms have been remedied in later versions of the software, including transactions and relational integrity constraints—features necessary to support “ACID properties” for relational databases, which allow the DBMS to ensure that client applications cannot interfere with one another or insert inconsistent values.[8]

Another criticism is MySQL’s divergence from the SQL standard on the subject of treatment of NULL values and default values. Its handling of dates allows storing a date with a day beyond the last day of a month with less than 31 days, and arithmetic operations are vulnerable to either integer overflow or floating point truncation.[9] Since version 5 of the server, the treatment of illegal values varies according to use of the “SQL Mode” set in the server, which is by default set to the unusually tolerant state that critics dislike.[10]

Earlier versions of the MySQL manual claimed that certain aspects of relational integrity checking and transactions that are common in most relational databases and yet missing in MySQL, were useless or even harmful, and that users were better off without them. Such statements drew the ire of SQL experts and MySQL today allows some support for previously-dismissed features.

When the beta version of MySQL 5.0 was released in March 2005, David Axmark, a co-founder of MySQL, said that “People have been criticizing MySQL since we started for not having stored procedures, triggers and views,” and “We’re fixing 10 years of criticism in one release.”[11] MySQL 5.0’s 13 October build 5.0.15 was released for production use on 24 October 2005, after more than two million downloads in the 5.0 beta cycle. MySQL version 5.0, however, does not currently guarantee ACID consistency in the case of a crash when some kinds of stored procedures or functions are used to modify the database.[12]

[edit] License issues

Some users have also criticized MySQL AB’s position on the licensing of the software. A few open source projects, such as Asterisk PBX, have reduced support for MySQL due to licensing concerns. Further, there was some controversy regarding the distribution of GPLed MySQL library files with other open source applications. The biggest controversy arose with PHP, which has a license incompatible with the GPL. This was later resolved when MySQL created a license exception that explicitly allows the inclusion of the MySQL client library in open source projects that are licensed under a number of OSI-compliant Open Source licenses, including the PHP license.[13]

In September 2005, MySQL AB and SCO forged a partnership for “joint certification, marketing, sales, training and business development work for a commercial version of the database for SCO’s new OpenServer 6 version of Unix”. SCO raised controversy beginning in 2003 with a number of high-profile patent lawsuits related to the Linux Operating System. Various MySQL employees expressed that the company was committed to serving its end users, regardless of their operating system choice, that the company would leave it to the courts to resolve the SCO licensing controversy, and that other common open source databases have also been ported to, and support, SCO OpenServer.

In October 2005, Oracle Corporation acquired Innobase OY, the Finnish company that developed the InnoDB storage engine that allows MySQL to provide such functionality as transactions and foreign keys. A press release by Oracle that was issued after the acquisition mentioned that the contracts that make the company’s software available to MySQL AB come up for renewal (and presumably renegotiation) some time in 2006. During the MySQL Users Conference in April 2006, MySQL issued a press release which confirmed that MySQL and Innobase OY agreed to a multi-year extension of their licensing agreement.[14]

In February 2006, Oracle Corporation acquired Sleepycat Software,[15] makers of the Berkeley DB, a database engine onto which another MySQL storage engine was built.

[edit] Trivia

  • The dolphin symbol in the MySQL logo was given the Swati name Sakila in October 2002 after a naming contest. [8]
  • MySQL was originally developed on Solaris.

[edit] History

  • MySQL was first released internally on May 23, 1995
  • Windows version released on January 8, 1998 for Windows 95 and NT
  • Version 3.23: beta from June 2000, production release January 2001
  • Version 4.0: beta from August 2002, production release March 2003 (unions)
  • Version 4.1: beta from June 2004, production release October 2004 (r-trees, subqueries)
  • Version 5.0: beta from March 2005, production release October 2005 (cursors, stored procedures, triggers, views, XA transactions)
  • Version 5.1: currently pre-production (since November 2005) (event scheduler, partitioning, plugin API, row-based replication, server log tables)
  • Version 5.2 will include foreign key support for all storage engines (at the moment only InnoDB supports this)

[edit] Prominent users

[edit] 2006 MySQL Application of the Year winners

  • Nokia, using MySQL Cluster to maintain real-time information about mobile network users.
  • flickr, Using MySQL to manage millions of photos and users.[12]
  • NetQOS, embeds MySQL to manage the world’s largest networks including Chevron, American Express and Boeing.

[edit] 2005 MySQL Application of the Year winners

  • CNET Networks
  • Friendster, more than 85 million dynamic page views per day, able to support more than 1.5 billion MySQL queries per day
  • Wikipedia, more than 200 million queries and 1.2 million updates per day with peak loads of 11,000 queries per second

[edit] See also


Wikibooks has more about this subject:


Free software

Free software Portal

One Response to “MySQL”

  1. My Home said

    This is very nice and informative post. I have bookmarked your site in order to find out your post in the future.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: