- Documentation Library
- Table of Contents
- MySQL 5.0 Manual
- Table of Contents
- C.3 Changements de la version 4.0.x (Production)
- C.3.1 Changements de la version 4.0.25 (pas encore publié)
- C.3.2 Changements de la version 4.0.24 (04 Mars 2005)
- C.3.3 Changements de la version 4.0.23 (18 Décembre 2004)
- C.3.4 Changements de la version 4.0.22 (27 Octobre 2004)
- C.3.5 Changements de la version 4.0.21
- C.3.6 Changements de la version 4.0.20
- C.3.7 Changements de la version 4.0.19 (04 mai 2004)
- C.3.8 Changements de la version 4.0.18 (pas encore publiée)
- C.3.9 Changements de la version 4.0.17 (14 décembre 2003)
- C.3.10 Changements de la version 4.0.16 (17 octobre 2003)
- C.3.11 Changements de la version 4.0.15 (03 septembre 2003)
- C.3.12 Changements de la version 4.0.14 (18 juillet 2003)
- C.3.13 Changements de la version 4.0.13 (16 Mai 2003)
- C.3.14 Changements de la version 4.0.12 (15 Mars 2003 : Production)
- C.3.15 Changements de la version 4.0.11 (20 Février 2003)
- C.3.16 Changements de la version 4.0.10 (29 janvier 2003)
- C.3.17 Changements de la version 4.0.9 (09 janvier 2003)
- C.3.18 Changements de la version 4.0.8 (07 janvier 2003)
- C.3.19 Changements de la version 4.0.7 (20 Décembre 2002)
- C.3.20 Changements de la version 4.0.6 (14 Décembre 2002 : Gamma)
- C.3.21 Changements de la version 4.0.5 (13 novembre 2002)
- C.3.22 Changements de la version 4.0.4 (29 septembre 2002)
- C.3.23 Changements de la version 4.0.3 (26 Août 2002 : Beta)
- C.3.24 Changements de la version 4.0.2 (01 Juillet 2002)
- C.3.25 Changements de la version 4.0.1 (23 décembre 2001)
- C.3.26 Changements de la version 4.0.0 (Octobre 2001 : alpha)
Fonctionnalité ajoutée ou modifiée :
Added
--with-big-tablescompilation option to configure. (Previously it was necessary to pass-DBIG_TABLESto the compiler manually in order to enable large table support.) Section 2.4.2, « Options habituelles deconfigure» for details.
Bogues corrigés :
Fixed a deadlock resulting from use of
FLUSH TABLES WITH READ LOCKwhile anINSERT DELAYEDstatement is in progress. (Bug#7823)Fixed a segmentation fault in mysqlcheck that occurred when the last table checked in
--auto-repairmode returned an error (such as the table being aMERGEtable). (Bug#9492)Fixed faulty display of
TIMESTAMPcolumns retrieved ascol_name+0newsystem variable is set to 1. (Bug#8894)Queries containing
CURRENT_USER()incorrectly were registered in the query cache. (Bug#9796)Fixed problems with static variables to allow building on Fedora Core 3. (Bug#6554)
An
UPDATEthat updated only some of the columns in a multiple-column index could result in a loop. (Bug#8942)REPAIR TABLEdid not invalidate query results in the query cache that were generated from the table. (Bug#8480)Fixed a bug that caused concurrent inserts to be allowed into the tables in the
SELECT ... UNION ...part ofINSERT ... SELECT ... UNION .... This could result in the incorrect order of queries in the binary log. (Bug#9922)Fixed a bug that under certain circumstances could allow a privilege escalation via database wildcards in
GRANT. (Bug#3924, CVE-2004-0957)<=>was not properly comparingNULLvalues in theWHEREclause of outer joins. (Bug#8711)InnoDB: Fixed a bug : MySQL-4.0.23 and 4.0.24 could complain that an InnoDB table created with MySQL-3.23.49 or earlier was in the new compact InnoDB table format of 5.0.3 or later, and InnoDB would refuse to use that table. (The same bug exists in 4.1.8 - 4.1.10.) There is nothing wrong with the table, it is mysqld that is in error. Workaround: wait that 4.0.25 or 4.1.11 is released before doing an upgrade, or dump the table and recreate it with any MySQL version >= 3.23.50 before upgrading to 4.0.23 or 4.0.24.
This is a translation of the MySQL Reference Manual that can be found at dev.mysql.com. The original Reference Manual is in English, and this translation is not necessarily as up to date as the English version.
