MySQL Reference Manual

Short Description
A relational database stores data in separate tables rather than putting all the data in one big storeroom. This adds speed and exibility. The tables are linked by defined relations making it possible to combine data from several tables on request. The SQL part of “MySQL” stands for “Structured Query Language” the most common standardised language used to access databases.

Website: lpf-esi.fe.up.pt | Filesize: 3437kb
No of Page(s): 833

Content
…
This section addresses the questions “How stable is MySQL Server?” and “Can I depend on MySQL Server in this project?” We will try to clarify these issues and answer some important questions that concern many potential users. The information in this section is based on data gathered from the mailing list, which is very active in identifying problems as well as reporting types of use.
Original code stems back from the early ’80s, providing a stable code base, and the ISAM tableformat remains backward-compatible. At TcX, the predecessor of MySQL AB, MySQL code has worked in projects since mid-1996, without any problems. When the MySQL Database Software was released to a wider public, we noticed that there were some pieces of “untested code” that were quickly found by the new users who made different types of queries from us. Each new release has had fewer portability problems (even though each new release has had many new features).
Each release of the MySQL Server has been usable. There have only been problems when users try code from the “gray zones.” Naturally, new users don’t know what the gray zones are; this section attempts to indicate those that are currently known. The descriptions mostly deal with Version 3.23 of MySQL Server. All known and reported bugs are fixed in the latest version, with the exception of those listed in the bugs section, which are things that are design-related.
…

Get the file Download here