Dyntex.net Support Centre: MySQL Reference Manual p.43

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 1: General Information 43 If you execute a PROCEDURE on a query that returns an empty set, in some cases the PROCEDURE will not transform the columns. Creation of a table of type MERGE doesn't check if the underlying tables are of compatible types. MySQL Server can't yet handle NaN, -Inf, and Inf values in double. Using these will cause problems when trying to export and import data. We should as an intermediate solution change NaN to NULL (if possible) and -Inf and Inf to the minimum respective maximum possible double value. LIMIT on negative numbers are treated as big positive numbers. If you use ALTER TABLE to rst add a UNIQUE index to a table used in a MERGE table and then use ALTER TABLE to add a normal index on the MERGE table, the key order will be dierent for the tables if there was an old key that was not unique in the table. This is because ALTER TABLE puts UNIQUE keys before normal keys to be able to detect duplicate keys as early as possible. The following are known bugs in earlier versions of MySQL: You can get a hung thread if you do a DROP TABLE on a table that is one among many tables that is locked with LOCK TABLES. In the following case you can get a core dump: Delayed insert handler has pending inserts to a table. LOCK table with WRITE. FLUSH TABLES. Before MySQL Server Version 3.23.2 an UPDATE that updated a key with a WHERE on the same key may have failed because the key was used to search for records and the same row may have been found multiple times: UPDATE tbl_name SET KEY=KEY+1 WHERE KEY > 100; A workaround is to use: mysql> UPDATE tbl_name SET KEY=KEY+1 WHERE KEY+0 > 100; This will work because MySQL Server will not use an index on expressions in the WHERE clause. Before MySQL Server Version 3.23, all numeric types where treated as xed-point elds. That means you had to specify how many decimals a oating-point eld shall have. All results were returned with the correct number of decimals. For platform-specic bugs, see the sections about compiling and porting. 1.8 MySQL and The Future (The TODO) This section lists the features that we plan to implement in MySQL Server. Everything in this list is approximately in the order it will be done. If you want to aect the priority order, please register a license or support us and tell us what you want to have done more quickly. See Section 1.4 [Licensing and Support], page 15.

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide