Направо към съдържанието

MySQL

от Уикипедия, свободната енциклопедия
Версия от 13:37, 5 октомври 2006 на Foxb (беседа | приноси) (Започнат превод)
(разл) ← По-стара версия | Текуща версия (разл) | По-нова версия → (разл)

Шаблон:Информация за програма MySQL is a multithreaded, multi-user, SQL Database Management System (DBMS) with more than six million installations.[1] MySQL AB makes MySQL available as free software under the GNU General Public License (GPL), but they also dual-license it under traditional proprietary licensing arrangements for cases where the intended use is incompatible with the GPL.

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 MySQL company also sells another DBMS, MaxDB, which is from an unrelated codebase.

Programming languages

There are APIs available that allow applications written in numerous programming languages to access MySQL databases, including: C, C++, C#, 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.

Uses

MySQL is popular for web applications such as MediaWiki or Drupal 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.) The claim made in many books is that MySQL is easier to learn and use than many other database applications. An example from the Dummies book is that you can quit MySQL with an obvious command of either exit or quit, although this is true for many other database applications.

Administration

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.

A widespread and popular alternative, written in PHP, is the free software web application phpMyAdmin.

Program specifications

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 more recent versions of Windows. A port of MySQL to OpenVMS is also available [2].

The latest production version

As of September 2006, MySQL offers production version 5.0.24a. It includes 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
  • INFORMATION_SCHEMA
  • 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
  • Full Unicode support
  • ACID compliance using the InnoDB, BDB and Cluster engines
  • Shared-nothing clustering through MySQL Cluster

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 for InnoDB).

The current MySQL 5.1 development release is 5.1.11 beta

Distinguishing features

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

  • Multiple storage engines (MyISAM, Merge, InnoDB, BDB, Memory/heap, Cluster, Federated, Archive, CSV, Blackhole and Example in 5.x), letting you choose the one which is most effective for each table in the application.
  • Commit grouping, gathering multiple transactions from multiple connections together to increase the number of commits per second.

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

Source code specifics

MySQL is written in 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.[4]

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 then the Community Edition of the MySQL Database Server engine. The Network maintains several levels of membership based on importance and urgency for response times.

Licensing

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 [5], 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. [6]

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

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

Pronunciation

"MySQL" is officially pronounced as "My Ess Queue Ell" [maɪ ɛs kjuː ɛl], not "My sequel" [maɪ siːkwəl] [9]. However, the company doesn't mind if others use either the "My sequel" form or other local variations if they are preferred by the speaker such as MySuckle.

The "My" portion of the name supposedly comes from the name of Monty's child [10], spelled "My" but pronounced in the local language as "mü" [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, which adheres to the official ANSI pronunciation but conflicts with the earlier IBM database of that name.[11]

The Swedish (MySQL AB is a Swedish company) word "Myskväll" (cozy evening, or even My's evening, "Mys kväll") is pronounced in a similar way but this might be a coincidence. Nevertheless this pronunciation is quite usual in Sweden.

Criticisms of MySQL

Шаблон:POV-section

Early versions of MySQL included few standard relational database management system (RDBMS) features, and the current production version still lacks many properties found in other SQL RDBMSs. This has led many database experts to criticize MySQL as falling short of being an RDBMS. Most relational theorists, such as Chris Date, Fabian Pascal, E.F. Codd, Hugh Darwen and their adherents would claim that because it falls short on several of Codd's 12 rules, like every other SQL DBMS, it shouldn't be considered relational.

Many of the early criticisms have been remedied in later versions of the software, including the lack of transactions and relational integrity constraints. These are features necessary to support the "ACID properties" for relational databases, which allow the DBMS to ensure that client applications cannot interfere with one another or insert inconsistent values. [12] Other criticisms include 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 ([13]). These values are treated according to the SQL standards in MySQL version 5 through the use of special SQL Modes.

Earlier versions of the MySQL manual included claims that certain missing features (considered essential for SQL-compliant RDBMSs) were useless or even harmful, and that users were better off without them. One section, entitled "Reasons NOT to use Foreign Keys constraints" [sic], advised users that relational-integrity checking was difficult to use and complicated a database application, and that its only useful purpose was to allow client software to diagram the relationships between database tables. [14] Another section claimed that a DBMS lacking transactions can provide data-integrity assurances as reliably as one supporting transactions—conflating the issue of transactional integrity with that of saving data when the database server loses power. [15] Since these claims contradicted basic principles of relational database design, they caused MySQL to be ridiculed by some database experts. Regardless of whether they were right or not, these claims are omitted in more recent versions of the manual. MySQL today allows some support for previously-dismissed features of relational integrity checking and transactions.

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 criticising MySQL since we started for not having stored procedures, triggers and views," and "We're fixing 10 years of criticism in one release." [16] 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.

Critics find MySQL's popularity surprising in the light of the existence of other open source database projects with comparable performance and in closer compliance to the SQL standards. MySQL advocates reply that the program serves its purpose for its users, who are willing to accept the program's limitations (which decrease with every major revision) in exchange for speed, simplicity and rapid development.

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

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

In February 2006, Oracle Corporation acquired Sleepycat Software [19], makers of the Berkeley DB, another storage engine used by MySQL.

Trivia

  • The dolphin symbol in the MySQL logo was given the Swati name на свази: Sakila in October 2002 after a naming contest. [20]

History

  • MySQL was first released internally on May 23, 1995
  • Windows version released on January 8, 1998 for Windows 95 and NT

Prominent users

  • Amazon.com - for many in-house projects
  • Cox Communications - the fourth largest cable-television provider in the United States, has more than 3,600 tables and two billion rows of data in their databases and handles approximately two million inserts every hour.
  • Craigslist
  • Digg - Popular news site.
  • Google - for the search engine's AdWords program
  • Gumtree - the UK's biggest classifieds site
  • LiveJournal - around 300 million page views per day
  • NASA - converted an Oracle-based acquisition system to MySQL [21]
  • Omniture
  • RightNow
  • Sabre, and its travel reservation system Travelocity
  • Slashdot - with around 50 million page views per day.
  • Yahoo! - for many mission-critical applications
  • 2006 MySQL Application of the Year winners
    • Nokia, using MySQL Cluster to maintain real-time information about mobile network users.
    • flickr, Using MySQL in a Scale-out architecture to manage millions of photos and users.
    • NetQOS, embeds MySQL to manage the worlds largest networks including Chevron, American Express and Boeing.
  • 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

See also

Шаблон:Portalpar

Documentation

Articles and guides

Online utilities using MySQL


Шаблон:Databases

bg:MySQL

Взето от „https://bg.wikipedia.org/w/index.php?title=MySQL&oldid=634531“.