From: jon Date: November 6 2007 4:29pm Subject: svn commit - mysqldoc@docsrva: r8554 - trunk/dynamic-docs/changelog List-Archive: http://lists.mysql.com/commits/37198 Message-Id: <200711061629.lA6GTtk0001245@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2007-11-06 17:29:54 +0100 (Tue, 06 Nov 2007) New Revision: 8554 Log: Consolidated some more redundant changelog entries. Modified: trunk/dynamic-docs/changelog/dupes.txt trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/dupes.txt =================================================================== --- trunk/dynamic-docs/changelog/dupes.txt 2007-11-06 14:46:49 UTC (rev 8553) +++ trunk/dynamic-docs/changelog/dupes.txt 2007-11-06 16:29:54 UTC (rev 8554) Changed blocks: 2, Lines Added: 24, Lines Deleted: 24; 736 bytes @@ -113,29 +113,29 @@ 14897x 14940x 15098x -15101 -15223 -15303 -15347 -15408 -15650 -15685 -15846 -15921 -15991 -16201 -16266 -16377 -16382 -16387 -16421 +15101x +15223x +15303x +15347x +15408x +15650x +15685x +15846x +15921x +15991x +16201x +16266x +16377x +16382x +16387x +16421x 16520x -16539 -16561 -16582 -16614 -16674 -16695 +16539x +16561x +16582x +16614x +16674x +16695x 16861 17047 17208 @@ -146,13 +146,13 @@ 17667 17671 17810 -17857 +17857x 17876 17926 18091x 18283 18298 -18359 +18359x 18361 18385 18386 Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-06 14:46:49 UTC (rev 8553) +++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-06 16:29:54 UTC (rev 8554) Changed blocks: 54, Lines Added: 224, Lines Deleted: 623; 27856 bytes @@ -6129,6 +6129,7 @@ + @@ -6137,15 +6138,16 @@ + - Performing a RENAME TABLE on an InnoDB table - when the server is started with the - option and the data - directory is a symlink caused a server crash. + Performing a RENAME TABLE on an + InnoDB table when the server was started with + the option and the data + directory was a symlink caused a server crash. @@ -11681,36 +11683,6 @@ - - - - - - - - - - - - - - - - - The length of the pattern string prefix for - LIKE operations was calculated incorrectly - for multi-byte character sets. As a result, the scanned range - was wider than necessary if the prefix contained any multi-byte - characters. - - - - - - - - - @@ -13728,8 +13700,9 @@ - + + @@ -16052,7 +16025,7 @@ - + @@ -26294,11 +26267,16 @@ - Certain subqueries where the inner query is the result of a - aggregate function would return different results on MySQL 5.0 - than on MySQL 4.1. + Certain subqueries where the inner query was the result of a + aggregate function would return different results with MySQL + ¤t-series; than with MySQL 4.1. + + Subselects could also return wrong results when the query cache + and grouping were involved. + + @@ -34721,7 +34699,7 @@ - + @@ -34733,11 +34711,21 @@ + - + + RPM packages had an incorrect zlib + dependency. + + + + + + + The original Linux RPM packages (5.0.17-0) had an issue with a zlib dependency that would result in an error during an install or upgrade. They were replaced by new @@ -45076,28 +45064,6 @@ - - - - - - - - - - - - Subselect could return wrong results when records cache and - grouping was involved. - - - - - - - - - @@ -47625,15 +47591,16 @@ + - Server crash when dropping InnoDB constraints - named - TABLENAME_ibfk_0. + Dropping InnoDB constraints named + tbl_name_ibfk_0 + could crash the server. @@ -49107,9 +49074,10 @@ + - + Triggers created in MySQL 5.0.16 and earlier could not be @@ -49118,6 +49086,15 @@ + + + + Triggers created in one version of the server could not be + dropped after upgrading to a newer version. + + + + @@ -53364,34 +53341,6 @@ - - - - - - - - - - - - - - - MySQL-shared-compat-4.1.15-0.i386.rpm, - MySQL-shared-compat-4.1.16-0.i386.rpm, and - MySQL-shared-compat-4.1.18-0.i386.rpm - incorrectly depended on glibc 2.3 and could - not be installed on a glibc 2.2 system. - - - - - - - - - @@ -55886,9 +55835,11 @@ + + - + The syntax for CREATE TRIGGER now includes a @@ -55897,26 +55848,38 @@ , for more information. - - Known issue: If you attempt to - replicate from a master server older than MySQL 5.0.17 to a - slave running MySQL 5.0.17 through 5.0.19, replication of - CREATE TRIGGER statements fails on the slave - with a Definer not fully qualified error. A - workaround is to create triggers on the master using a - version-specific comment embedded in each CREATE - TRIGGER statement: - + + Known issue + + If you attempt to replicate from a master server older than + MySQL 5.0.17 to a slave running MySQL 5.0.17 through 5.0.19, + replication of CREATE TRIGGER statements + fails on the slave with a Definer not fully + qualified error. A workaround is to create + triggers on the master using a version-specific comment + embedded in each CREATE TRIGGER statement: CREATE /*!50017 DEFINER = 'root'@'localhost' */ TRIGGER ... ; + CREATE TRIGGER statements written this way + will replicate to newer slaves, which pick up the + DEFINER clause from the comment and execute + successfully. + + + + + + + - CREATE TRIGGER statements written this way - will replicate to newer slaves, which pick up the - DEFINER clause from the comment and execute - successfully. + Triggers from older servers that included no + DEFINER clause in the trigger definition now + execute with the privileges of the invoker (which on the slave + is the slave SQL thread). Previously, replication slaves could + not replicate such triggers. @@ -57543,33 +57506,6 @@ - - - - - - - - - - - - - - - - - - - If an abort by the Transaction Coordinator timed out, the abort - condition was incorrectly handled, causing the transacviton - record to be released prematurely. - - - - - - @@ -61847,6 +61783,7 @@ + @@ -64702,6 +64639,7 @@ + @@ -69333,6 +69271,7 @@ + @@ -73466,14 +73405,15 @@ + - Corrected race condition when dropping the adaptive hash index - for a B-tree page in InnoDB. + A race condition could occur when dropping the adaptive hash + index for a B-tree page in InnoDB. @@ -76256,27 +76196,6 @@ - - - - - - - - - - - - Server crash when dropping InnoDB constraints named - TABLENAME_ibfk_0. - - - - - - - - @@ -80366,35 +80285,6 @@ - - - - - - - - - - - - - - - - - Performing a RENAME TABLE on an - InnoDB table when the server is started with - the option and the data - directory is a symlink caused a server crash. - - - - - - - - - @@ -81329,7 +81219,8 @@ - Patch reverted. + A patch fixing the omission of leading zeros in dates in MySQL + 4.1.21 was reverted. @@ -81534,12 +81425,7 @@ - - - - - @@ -81548,7 +81434,7 @@ - + @@ -81556,21 +81442,55 @@ Due to a change in the naming scheme for partitioning and subpartitioning files, it is not possible for the server to read - partitioned tables created in previous MySQL versions. A - suggested workaround is (1) to create a non-partitioned table - with the same table schema using a standard CREATE - TABLE statement (that is, with no partitioning - clauses) and then (2) to issue a SELECT INTO - to copy the data into the non-partitioned table before the - upgrade; following the upgrade, you can partition the new table - using ALTER TABLE ... PARTITION BY .... - Alternatively, you can dump the table using - mysqldump prior to upgrading and reload it - afterwards with LOAD DATA. In either case, - you should drop the pre-5.1.6 partitioned tables before - upgrading to 5.1.6 or later. + partitioned tables created in previous MySQL versions. + Attempting to read pre-5.1.6 partitioned tables with a MySQL + 5.1.7 or later server now generates a suitable warning message. + + Two possible workarounds are: + + + + + + + + + Create a non-partitioned table with the same table + schema using a standard CREATE + TABLE statement (that is, with no + partitioning clauses) + + + + + + Issue a SELECT INTO to copy the + data into the non-partitioned table before the + upgrade + + + + + Following the upgrade, you can partition the new table + using ALTER TABLE ... PARTITION BY .... + + + + + + Alternatively, you can dump the table using + mysqldump prior to upgrading and reload + it afterwards with LOAD DATA. + + + + + In either case, you should drop the pre-5.1.6 partitioned tables + before upgrading to 5.1.6 or later. + + If any partitioned tables that were created prior to MySQL @@ -81579,9 +81499,28 @@ INFORMATION_SCHEMA.PARTITIONS table, nor will you be able to drop those tables or the database or databases in which they are located. In this event, you must: - (1) shut down mysqld; (2) manually delete - the table, partition, and (if any) subpartition files; and - then (3) restart the MySQL Server. + + + + + Shut down mysqld + + + + + + Manually delete the table, partition, and (if any) + subpartition files + + + + + + Restart the MySQL Server + + + + @@ -82891,37 +82830,6 @@ - - - - - - - - - - - - - - - - - - Attempting to read pre-5.1.6 partitioned tables with a MySQL - 5.1.7 (or later) server now generates a suitable warning - message. - - - - For additional information about this issue, see - . - - - - - - @@ -84801,6 +84709,7 @@ + @@ -85131,32 +85040,6 @@ - - - - - - - - - - - - - - - - SELECT with GROUP BY on a - view can cause a server crash. - - - - - - - - - @@ -90651,9 +90534,10 @@ - - + + + @@ -90665,6 +90549,16 @@ + + + + A problem with takeover during a system restart caused ordered + indexes to be rebuilt incorrectly. This also adversely affected + MySQL Cluster Replication. + + + + @@ -95941,37 +95835,6 @@ - - - - - - - - - - - - - - - - - - Replication slaves could not replicate triggers from older - servers that included no DEFINER clause in - the trigger definition. Now the trigger executes with the - privileges of the invoker (which on the slave is the slave SQL - thread). - - - - - - - - - @@ -98141,6 +98004,7 @@ + @@ -98149,9 +98013,9 @@ The index_merge/Intersection - optimizer could have a memory overrun when the number of table - columns covered by an index is sufficiently large, possibly - resulting in a server crash. + optimizer could experience a memory overrun when the number of + table columns covered by an index was sufficiently large, + possibly resulting in a server crash. @@ -99474,9 +99338,10 @@ + - + All subpartitions within a given partitioned table are now @@ -99485,6 +99350,15 @@ + + + + Names of subpartitions must now be unique for an entire table, + and not merely within the same partition. + + + + @@ -105088,27 +104962,6 @@ - - - - - - - - - - - - - - Corrected race condition when dropping the adaptive hash index - for a B-tree page in InnoDB. - - - - - - @@ -105448,31 +105301,6 @@ - - - - - - - - - - - - - - - perror did not properly report NDB error - codes. - - - - - - - - - @@ -110670,32 +110498,6 @@ - - - - - - - - - - - - - - - MySQL-shared-compat-5.1.9-0.i386.rpm - incorrectly depended on glibc 2.3 and could - not be installed on a glibc 2.2 system. - - - - - - - - - @@ -113827,36 +113629,6 @@ - - - - - - - - - - - - - - - - - - - - - Added the option to - mysqld to enable SYSDATE() - to be treated as an alias for NOW(). See - . - - - - - - @@ -114264,35 +114036,7 @@ - - - - - - - - - - - - - - - - - A problem with takeover during a system restart caused ordered - indexes to be rebuilt incorrectly. This also adversely affected - Cluster Replication. - - - - - - - - - @@ -114354,6 +114098,22 @@ + + + + The omission of leading zeros in dates could lead to erroneous + results when these were compared with the output of certain date + and time functions. + + + + + The patch for this bug was reverted in MySQL 4.1.22. + + + + + @@ -114857,8 +114617,9 @@ - + + @@ -116977,27 +116738,6 @@ - - - - - - - - - - - - - - Names of subpartitions must now be unique for an entire table, - and not merely within the same partition. - - - - - - @@ -119769,35 +119509,6 @@ - - - - - - - - - - - - - - - - The - index_merge/Intersection - optimizer could have a memory overrrun when the number of table - columns covered by an index is sufficiently large, possibly - resulting in a server crash. - - - - - - - - - @@ -121944,33 +121655,7 @@ - - - - - - - - - - - - - - - - The mysql_close() C API - function leaked handles for share-memory connections on Windows. - - - - - - - - - @@ -122461,33 +122146,6 @@ - - - - - - - - - - - - - - - - - - - - The effects of scheduled events were not replicated (that is, - binary logging of scheduled events did not work). - - - - - - @@ -124639,32 +124297,7 @@ - - - - - - - - - - - - - - - Triggers created in one version of the server could not be - dropped after upgrading to a newer version. - - - - - - - - - @@ -129754,33 +129387,7 @@ - - - - - - - - - - - - - - - - RPM packages had an incorrect zlib - dependency. - - - - - - - - - @@ -133780,12 +133387,26 @@ + + - + + MySQL-shared-compat-4.1.15-0.i386.rpm, + MySQL-shared-compat-4.1.16-0.i386.rpm, and + MySQL-shared-compat-4.1.18-0.i386.rpm + incorrectly depended on glibc 2.3 and could + not be installed on a glibc 2.2 system. + + + + + + + MySQL-shared-compat-5.0.13-0.i386.rpm, MySQL-shared-compat-5.0.15-0.i386.rpm, MySQL-shared-compat-5.0.18-0.i386.rpm, @@ -133798,6 +133419,16 @@ + + + + MySQL-shared-compat-5.1.9-0.i386.rpm + incorrectly depended on glibc 2.3 and could + not be installed on a glibc 2.2 system. + + + + @@ -133986,37 +133617,6 @@ - - - - - - - - - - - - - - - - - - A DELETE statement involving a LEFT - JOIN and an IS NULL test on the - right-hand table of the join crashed the server when the - innodb_locks_unsafe_for_binlog option was - enabled. - - - - - - - - - @@ -136685,6 +136285,7 @@ +