1 General Information

The MySQL (R) software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. MySQL is a trademark of MySQL AB.

The MySQL software is Dual Licensed. Users can choose to use the MySQL software as an Open Source/Free Software product under the terms of the GNU General Public License (http://www.gnu.org/licenses/) or can purchase a standard commercial license from MySQL AB. See section 1.4 MySQL Support and Licensing.

The MySQL web site (http://www.mysql.com/) provides the latest information about the MySQL software.

The following list describes some sections of particular interest in this manual:

• For information about the company behind the MySQL Database Server, see section 1.3 What Is MySQL AB?.
• For a discussion about the capabilities of the MySQL Database Server, see section 1.2.2 The Main Features of MySQL.
• For installation instructions, see section 2 MySQL Installation.
• For tips on porting the MySQL Database Software to new architectures or operating systems, see section E Porting to Other Systems.
• For information about upgrading from a Version 4.0 release, see section 2.5.1 Upgrading From Version 4.0 to 4.1.
• For information about upgrading from a Version 3.23 release, see section 2.5.2 Upgrading From Version 3.23 to 4.0.
• For information about upgrading from a Version 3.22 release, see section 2.5.3 Upgrading From Version 3.22 to 3.23.
• For a tutorial introduction to the MySQL Database Server, see section 3 Tutorial Introduction.
• For examples of SQL and benchmarking information, see the benchmarking directory (`sql-bench' in the distribution).
• For a history of new features and bug fixes, see section D MySQL Change History.
• For a list of currently known bugs and misfeatures, see section 1.8.6 Known Errors and Design Deficiencies in MySQL.
• For future plans, see section 1.9 MySQL and The Future (The TODO).
• For a list of all the contributors to this project, see section C Credits.

Important:

Reports of errors (often called bugs), as well as questions and comments, should be sent to the mailing list at mysql@lists.mysql.com. See section 1.7.1.3 How to Report Bugs or Problems.

The mysqlbug script should be used to generate bug reports on Unix. (Windows distributions contain a file `mysqlbug.txt' in the base directory that can be used as a template for a bug report.)

For source distributions, the mysqlbug script can be found in the `scripts' directory. For binary distributions, mysqlbug can be found in the `bin' directory (`/usr/bin' for the MySQL-server RPM package).

If you have found a sensitive security bug in MySQL Server, you should send an e-mail to security@mysql.com.

Subsections

• 1.1 About This Manual
• 1.1.1 Conventions Used in This Manual
• 1.2 What Is MySQL?
• 1.2.1 History of MySQL
• 1.2.2 The Main Features of MySQL
• 1.2.3 How Stable Is MySQL?
• 1.2.4 How Big Can MySQL Tables Be?
• 1.2.5 Year 2000 Compliance
• 1.3 What Is MySQL AB?
• 1.3.1 The Business Model and Services of MySQL AB
• 1.3.1.1 Support
• 1.3.1.2 Training and Certification
• 1.3.1.3 Consulting
• 1.3.1.4 Commercial Licenses
• 1.3.1.5 Partnering
• 1.3.1.6 Advertising
• 1.3.2 Contact Information
• 1.4 MySQL Support and Licensing
• 1.4.1 Support Offered by MySQL AB
• 1.4.2 Copyrights and Licenses Used by MySQL
• 1.4.3 MySQL Licenses
• 1.4.3.1 Using the MySQL Software Under a Commercial License
• 1.4.3.2 Using the MySQL Software for Free Under GPL
• 1.4.4 MySQL AB Logos and Trademarks
• 1.4.4.1 The Original MySQL Logo
• 1.4.4.2 MySQL Logos that may be Used Without Written Permission
• 1.4.4.3 When do you need a Written Permission to use MySQL Logos?
• 1.4.4.4 MySQL AB Partnership Logos
• 1.4.4.5 Using the word MySQL in Printed Text or Presentations
• 1.4.4.6 Using the word MySQL in Company and Product Names
• 1.5 MySQL 4.0 In A Nutshell
• 1.5.1 Features Available in MySQL 4.0
• 1.5.2 Embedded MySQL Server
• 1.6 MySQL 4.1 In A Nutshell
• 1.6.1 Features Available in MySQL 4.1
• 1.6.2 Stepwise Rollout
• 1.6.3 Ready for Immediate Development Use
• 1.6.4 MySQL 5.0, The Next Development Release
• 1.7 MySQL Information Sources
• 1.7.1 MySQL Mailing Lists
• 1.7.1.1 The MySQL Mailing Lists
• 1.7.1.2 Asking Questions or Reporting Bugs
• 1.7.1.3 How to Report Bugs or Problems
• 1.7.1.4 Guidelines for Answering Questions on the Mailing List
• 1.7.2 MySQL Community Support on IRC (Internet Relay Chat)
• 1.8 How Standards-compatible Is MySQL?
• 1.8.1 What Standards Does MySQL Follow?
• 1.8.2 Running MySQL in ANSI Mode
• 1.8.3 MySQL Extensions To The SQL-92 Standard
• 1.8.4 MySQL Differences Compared To SQL-92
• 1.8.4.1 Subqueries
• 1.8.4.2 SELECT INTO TABLE
• 1.8.4.3 Transactions and Atomic Operations
• 1.8.4.4 Stored Procedures and Triggers
• 1.8.4.5 Foreign Keys
• 1.8.4.6 Views
• 1.8.4.7 `--' as the Start of a Comment
• 1.8.5 How MySQL deals with constraints
• 1.8.5.1 Constraint PRIMARY KEY / UNIQUE
• 1.8.5.2 Constraint NOT NULL and DEFAULT values
• 1.8.5.3 Constraint ENUM and SET
• 1.8.6 Known Errors and Design Deficiencies in MySQL
• 1.8.6.1 Errors in 3.23 Fixed in a Later MySQL Version
• 1.8.6.2 Open Bugs / Design Deficiencies in MySQL
• 1.9 MySQL and The Future (The TODO)
• 1.9.1 New Features Planned For 4.1
• 1.9.2 New Features Planned For 5.0
• 1.9.3 New Features Planned For 5.1
• 1.9.4 New Features Planned For The Near Future
• 1.9.5 New Features Planned For The Mid-Term Future
• 1.9.6 New Features We Don't Plan To Do
• 1.10 How MySQL Compares to Other Databases
• 1.10.1 How MySQL Compares to mSQL
• 1.10.1.1 How to Convert mSQL Tools for MySQL
• 1.10.1.2 How mSQL and MySQL Client/Server Communications Protocols Differ
• 1.10.1.3 How mSQL 2.0 SQL Syntax Differs from MySQL
• 1.10.2 How MySQL Compares to PostgreSQL
• 1.10.2.1 MySQL and PostgreSQL development strategies
• 1.10.2.2 Featurewise Comparison of MySQL and PostgreSQL
• 1.10.2.3 Benchmarking MySQL and PostgreSQL

User Comments

Add your own comment.