| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | July 25 2008 5:44am |
| Subject: | svn commit - mysqldoc@docsrva: r11371 - trunk/dynamic-docs/changelog | ||
| View as plain text | |||
Author: jstephens Date: 2008-07-25 05:44:12 +0200 (Fri, 25 Jul 2008) New Revision: 11371 Log: Last night's WL#4169 edits (patch 4 in a series, collect them all) Modified: trunk/dynamic-docs/changelog/mysqld.xml Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2008-07-25 02:20:59 UTC (rev 11370) +++ trunk/dynamic-docs/changelog/mysqld.xml 2008-07-25 03:44:12 UTC (rev 11371) Changed blocks: 74, Lines Added: 208, Lines Deleted: 228; 32740 bytes @@ -39860,6 +39860,8 @@ </logentry> +<!-- WL#4169 EDITS THROUGH HERE --> + <logentry entrytype="bug"> <tags> @@ -39905,12 +39907,11 @@ <message> <para> - Fixed a bug in replication that caused the master to stamp - generated statements (such as <literal>SET</literal> commands) - with an <literal>error_code</literal> intended only for another - statement. This could happen, for example, when a statements - generates a duplicate key error on the master but must be - replicated. + A replication master stamped a generated statement (such as a + <literal>SET</literal> statement) with an error code intended + only for another statement. This could happen, for example, when + a statement generated a duplicate key error on the master but + still had be to replicated to the slave. </para> </message> @@ -39959,9 +39960,9 @@ <message> <para> - Fixed a bug that could cause "Record has changed since last - read in table" error message in some queries on - <literal>HEAP</literal> tables that contain only one row. + A spurious <errortext>Record has changed since last read in + table</errortext> error could be raised by some queries on + <literal>HEAP</literal> tables containing only one row. </para> </message> @@ -40036,9 +40037,9 @@ <message> <para> - Fixed a bug in client-side conversion of string column to - <literal>MYSQL_TIME</literal> application buffer (prepared - statements API). + Conversion of a client-side string column to a + <literal>MYSQL_TIME</literal> application buffer was not handled + correctly by the prepared statements API. </para> </message> @@ -40228,10 +40229,9 @@ <message> <para> - Fixed handling of table-name matching in - <command>mysqlhotcopy</command> to accommodate - <literal>DBD::mysql</literal> 2.9003 and up (which implement - identifier quoting). + Matching of table names by <command>mysqlhotcopy</command> now + accommodates <literal>DBD::mysql</literal> versions 2.9003 and + up, which implement identifier quoting. </para> </message> @@ -40334,8 +40334,7 @@ <message> <para> - Fixed a failure of <literal>WITH ROLLUP</literal> to sum values - properly. + <literal>WITH ROLLUP</literal> did not sum values properly. </para> </message> @@ -40632,19 +40631,17 @@ </para> <para> - It should be noted that, in such cases, both the warning and the - increase in the <option>--table-open-cache</option> value were - completely harmless. Note also that it is not possible for the - MySQL Server to predict or to control limitations on the maximum - number of open files, since this is determined by the operating - system. + In such cases, both the warning and the increase in the + <option>--table-open-cache</option> value were completely + harmless. Note also that it is not possible for the MySQL Server + to predict or to control limitations on the maximum number of + open files, since this is determined by the operating system. </para> <para> - The recalculation code has now been fixed to ensure that the - value of <option>--table-open-cache</option> is no longer - increased automatically, and that a warning is now given only if - some values had to be decreased due to operating system limits. + The value of <option>--table-open-cache</option> is no longer + increased automatically, and a warning is now given only if some + values had to be decreased due to operating system limits. </para> </message> @@ -41136,8 +41133,8 @@ <message> <para> - Fixed a bug with the <function role="sql">INTERVAL()</function> - function when 8 or more comparison arguments are provided. + The <function role="sql">INTERVAL()</function> function did not + work correctly when 8 or more comparison arguments were used. </para> </message> @@ -41556,11 +41553,10 @@ <message> <para> - Fixed slave SQL thread so that the <literal>SET - COLLATION_SERVER...</literal> statements it replicates don't - advance its position (so that if it gets interrupted before the - actual update query, it later redoes the - <literal>SET</literal>). + <literal>SET COLLATION_SERVER...</literal> statements replicated + by the slave SQL thread no longer advance its position. This is + so that, if the thread is interrupted before the update is + completed, it later performs the <literal>SET</literal> again. </para> </message> @@ -41641,9 +41637,8 @@ <message> <para> - Fixed a server crash when creating a <literal>PRIMARY - KEY</literal> for a table, if the table contained a - <literal>BIT</literal> column. + Creating a <literal>PRIMARY KEY</literal> on a table having a + <literal>BIT</literal> column caused the server to crash. </para> </message> @@ -42297,8 +42292,8 @@ <message> <para> - Fixed bug in prepared <literal>EXPLAIN</literal> statement which - led to server crash. + Prepared <literal>EXPLAIN</literal> statements could lead to a + server crash. </para> </message> @@ -42460,10 +42455,11 @@ <message> <para> - Fixed a crash when a <literal>SELECT</literal> that required a - temporary table (marked by <literal>Using temporary</literal> in - <literal>EXPLAIN</literal> output) was used as a derived table - in <literal>EXPLAIN</literal> command. + A <literal>SELECT</literal> that required a temporary table + (marked by <literal>Using temporary</literal> in + <literal>EXPLAIN</literal> output) and was used as a derived + table in <literal>EXPLAIN</literal> command caused the server to + crash. </para> </message> @@ -42767,12 +42763,12 @@ <message> <para> - Fixed prepared statement support for <literal>INSERT</literal>, + Prepared statements are supported for <literal>INSERT</literal>, <literal>REPLACE</literal>, <literal>CREATE</literal>, <literal>DELETE</literal>, <literal>SELECT</literal>, <literal>DO</literal>, <literal>SET</literal> and - <literal>SHOW</literal>. All other commands are prohibited via - prepared statement interface. + <literal>SHOW</literal> statements. All other statements are now + prohibited by the prepared statement interface. </para> </message> @@ -42853,8 +42849,9 @@ <message> <para> - The <option>--plugin_dir</option> option was not working. Also - fix error with specifying parser name for fulltext. + The <option>--plugin_dir</option> option was not working. + Specifying the parser name for fulltext also did not work + correctly. </para> </message> @@ -42879,9 +42876,8 @@ <message> <para> - Fixed a problem with accented letters improperly being treated - as distinct with the <literal>utf_general_ci</literal> - collation. + Accented letters were improperly treated as distinct by the + <literal>utf_general_ci</literal> collation. </para> </message> @@ -43072,9 +43068,8 @@ <message> <para> - Fixed a bug in authentication code that allowed a malicious user - to bypass password verification with specially crafted packets, - using a modified client library. + A malicious user could bypass password verification with + specially crafted packets, using a modified client library. </para> </message> @@ -43619,9 +43614,9 @@ <message> <para> - Fixed a bug in execution of subqueries in <literal>SET</literal> - and <literal>DO</literal> statements which caused wrong results - to be returned from subsequent queries. + Execution of subqueries in <literal>SET</literal> and + <literal>DO</literal> statements caused wrong results to be + returned from subsequent queries. </para> </message> @@ -43800,8 +43795,8 @@ <message> <para> - Fixed a segmentation fault when running <literal>LOAD DATA FROM - MASTER</literal> after <literal>RESET SLAVE</literal>. + Running <literal>LOAD DATA FROM MASTER</literal> after + <literal>RESET SLAVE</literal> caused a segmentation fault. </para> </message> @@ -43878,8 +43873,8 @@ <message> <para> - Fixed handling of floats and doubles when using prepared - statement API in the embedded server. + Floats and doubles were not handled correctly when using the + prepared statement API in the embedded server. </para> </message> @@ -44686,9 +44681,10 @@ <message> <para> - Fixed a crash when using <literal>TIMESTAMP</literal> columns - with no minute or second parts in <literal>GROUP BY</literal> - with the <literal>new</literal> system variable set to 1. + Using <literal>TIMESTAMP</literal> columns with no minute or + second parts in <literal>GROUP BY</literal> clauses with the + <literal>new</literal> system variable set to 1 caused the + server to crash. </para> </message> @@ -44988,12 +44984,11 @@ <message> <para> - Fixed <literal>utf8_spanish2_ci</literal> and - <literal>ucs2_spanish2_ci</literal> collations to not consider - <quote> <literal>r</literal> </quote> equal to <quote> - <literal>rr</literal> </quote>. If you upgrade to this version - from an earlier version, you should rebuild the indexes of - affected tables. + The <literal>utf8_spanish2_ci</literal> and + <literal>ucs2_spanish2_ci</literal> collations no longer + consider <literal>r</literal> equal to <literal>rr</literal> . + If you upgrade to this version from an earlier version, you + should rebuild the indexes of any affected tables. </para> </message> @@ -45127,9 +45122,8 @@ <message> <para> - Fixed a crashing bug in <literal>DERIVED TABLES</literal> when - <literal>EXPLAIN</literal> is used on a <literal>DERIVED - TABLES</literal> with a join. + Using <literal>EXPLAIN</literal> on a derived table with a join + caused the server to crash. </para> </message> @@ -45857,9 +45851,8 @@ <message> <para> - Fixed a bug that under certain circumstances could allow a - privilege escalation via database wildcards in - <literal>GRANT</literal>. + Privileges could be escalated via database wildcards in + <literal>GRANT</literal> statements. </para> </message> @@ -45910,8 +45903,8 @@ <message> <para> - Fixed check of <literal>EXPLAIN</literal> of - <literal>UNION</literal>. + <literal>EXPLAIN</literal> should now work correctly with + <literal>UNION</literal> queries. </para> </message> @@ -46120,9 +46113,9 @@ <message> <para> - Fixed a server crash resulting from repeated calls to - <function role="sql">ABS()</function> when the argument - evaluated to <literal>NULL</literal>. + Repeated calls to <function role="sql">ABS()</function> when the + argument evaluated to <literal>NULL</literal> crashed the + server. </para> </message> @@ -46225,11 +46218,9 @@ <message> <para> - <literal>InnoDB</literal>: Fix a race condition that could cause - the assertion <literal>space->n_pending_flushes == - 0</literal> to fail in <filename>fil0fil.c</filename>, in - <literal>fil_space_free()</literal>, in <literal>DROP - TABLE</literal> or in <literal>ALTER TABLE</literal>. + <literal>InnoDB</literal>: A rare race condition could cause an + assertion in <literal>DROP TABLE</literal> or in <literal>ALTER + TABLE</literal>. </para> </message> @@ -46652,8 +46643,8 @@ <message> <para> - Fixed a bug in <command>my_print_defaults</command> that made it - ignore the <option>--defaults-extra-file</option> and + <command>my_print_defaults</command> ignored the + <option>--defaults-extra-file</option> and <option>--defaults-file</option> options. </para> @@ -47918,10 +47909,10 @@ <message> <para> - Fixed a problem where <literal>ALTER TABLE</literal> on a - <literal>TEMPORARY</literal> table with a mixed-lettercase name - could cause the table to disappear when - <literal>lower_case_table_names</literal> was set to 2. + <literal>ALTER TABLE</literal> on a <literal>TEMPORARY</literal> + table with a mixed-lettercase name could cause the table to + disappear when <literal>lower_case_table_names</literal> was set + to 2. </para> </message> @@ -48001,7 +47992,8 @@ <message> <para> - Fixed problem with <literal>NULL</literal> and derived tables. + <literal>NULL</literal> was not handled correctly with derived + tables. </para> </message> @@ -48026,9 +48018,8 @@ <message> <para> - Fixed a problem creating the result set for a - <literal>UNION</literal> that involved long string values. - Values were not being converted correctly to + For a <literal>UNION</literal> that involved long string values, + values were not being converted correctly to <literal>TEXT</literal> values. </para> @@ -48233,11 +48224,11 @@ <message> <para> - Fix for a bug in <literal>UNION</literal> operations with + <literal>UNION</literal> operations with the <literal>InnoDB</literal> storage engine, when some columns from one table were used in one <literal>SELECT</literal> statement and some were used in another <literal>SELECT</literal> - statement. + statement, were not handled correctly. </para> </message> @@ -48315,9 +48306,9 @@ <message> <para> - Fixed a bug that caused incorrect results for complex datetime - expressions containing casts of datetime values to - <literal>TIME</literal> or <literal>DATE</literal> values. + Incorrect results were obtained for complex datetime expressions + containing casts of datetime values to <literal>TIME</literal> + or <literal>DATE</literal> values. </para> </message> @@ -48503,12 +48494,12 @@ <message> <para> - Fixed a bug with <literal>INSERT</literal> for a table with - <literal>FULLTEXT</literal> indexes. Under rare circumstances, - this could result in a corrupted table if words of different - lengths may be considered equal. This is possible in some - collations, for example, in <literal>utf8_general_ci</literal> - or <literal>latin1_german2_ci</literal>. + <literal>INSERT</literal> on a table with + <literal>FULLTEXT</literal> indexes, could under rare + circumstances result in a corrupted table if words of different + lengths could be considered equal. This is possible in some + collations such as <literal>utf8_general_ci</literal> and + <literal>latin1_german2_ci</literal>. </para> </message> @@ -48726,6 +48717,7 @@ <logentry entrytype="bug"> <tags> + <highlight type="securityfix"/> <manual type="SSL"/> <manual type="REQUIRE SSL"/> </tags> @@ -48737,9 +48729,9 @@ <message> <para> - Fixed a security bug: A server compiled without SSL support - still allowed connections by users who had the <literal>REQUIRE - SSL</literal> option specified for their accounts. + A server compiled without SSL support still allowed connections + by users who had the <literal>REQUIRE SSL</literal> option + specified for their accounts. </para> </message> @@ -48820,9 +48812,9 @@ <message> <para> - Fixed a bug which caused server crash if query containing + Praparing a query using the <function role="sql">CONVERT_TZ()</function> function with - constant arguments was prepared. + constant arguments caused the server to crash. </para> </message> @@ -48843,10 +48835,9 @@ <message> <para> - <literal>InnoDB</literal>: Fixed a bug: - <literal>InnoDB</literal> failed to drop a table in the - background drop queue if the table was referenced by a - <literal>FOREIGN KEY</literal> constraint. + <literal>InnoDB</literal>: <literal>InnoDB</literal> failed to + drop a table in the background drop queue if the table was + referenced by a <literal>FOREIGN KEY</literal> constraint. </para> </message> @@ -49011,8 +49002,8 @@ <message> <para> - Fixed a bug in <literal>PROCEDURE ANALYSE()</literal>, which did - not quote some <literal>ENUM</literal> values properly. + <literal>PROCEDURE ANALYSE()</literal> did not quote some + <literal>ENUM</literal> values properly. </para> </message> @@ -49672,14 +49663,14 @@ <message> <para> - Fixed a bug in <literal>MERGE</literal> tables created with - <literal>INSERT_METHOD=LAST</literal>, that were not able to - report a key number that caused <quote>Duplicate entry</quote> - error for <literal>UNIQUE</literal> key in - <literal>INSERT</literal>. As a result, error message was not - precise enough (error 1022 instead of error 1062) and - <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal> did not - work. + <literal>MERGE</literal> tables created with + <literal>INSERT_METHOD=LAST</literal> were not able to report a + key number, causing <errortext>Duplicate entry</errortext> + errors for <literal>UNIQUE</literal> keys in + <literal>INSERT</literal> statements. As a result, the error + message was not precise enough (error 1022 instead of error + 1062) and <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal> + did not work. </para> </message> @@ -50014,8 +50005,8 @@ <message> <para> - Fixed bug with <literal>SHOW CREATE TABLE ...</literal> which - didn't properly double quotes. + <literal>SHOW CREATE TABLE ...</literal> did not properly double + quotes. </para> </message> @@ -50088,10 +50079,10 @@ <message> <para> - Fixed a bug in <literal>CREATE ... SELECT</literal> that - sometimes caused a string column with a multi-byte character set - (such as <literal>utf8</literal>) to have insufficient length to - hold the data. + <literal>CREATE ... SELECT</literal> sometimes created a string + column with a multi-byte character set (such as + <literal>UTF8</literal>) of insufficient length for holding the + data. </para> </message> @@ -50793,12 +50784,11 @@ <message> <para> - <literal>InnoDB</literal>: Fixed a bug that caused - <literal>CREATE TEMPORARY TABLE ... ENGINE=InnoDB</literal> to - terminate <command>mysqld</command> when running in - <literal>innodb_file_per_table</literal> mode. Per-table - tablespaces for temporary tables from now on are created in the - temporary directory of <command>mysqld</command>. + <literal>InnoDB</literal>: <literal>CREATE TEMPORARY TABLE ... + ENGINE=InnoDB</literal> terminated <command>mysqld</command> + when running in <literal>innodb_file_per_table</literal> mode. + Now, per-table for temporary tables are created in the temporary + directory used by <command>mysqld</command>. </para> </message> @@ -51272,8 +51262,8 @@ <message> <para> - Fixed a bug of using parameters in some prepared statements via - SQL syntax. + Parameters in some prepared statements were not handled + correctly. </para> </message> @@ -51575,8 +51565,8 @@ <message> <para> - Fixed crash on second execution of prepared statement with - <literal>UNION</literal>. + The second execution of a prepared statement using + <literal>UNION</literal> caused the server to crash. </para> </message> @@ -52294,6 +52284,7 @@ <logentry entrytype="bug"> <tags> + <highlight type="securityfix"/> <manual type="INFORMATION_SCHEMA"/> </tags> @@ -52308,9 +52299,8 @@ <message> <para> - Fixed a permissions problem whereby information in - <literal>INFORMATION_SCHEMA</literal> could be exposed to a user - with insufficient privileges. + Information in <literal>INFORMATION_SCHEMA</literal> could be + exposed to a user with insufficient privileges. </para> </message> @@ -52392,8 +52382,8 @@ <message> <para> - Fixed table corruption bug when using <literal>INSERT - DELAYED</literal> with prepared statements. + Using <literal>INSERT DELAYED</literal> with prepared statements + could lead to table corruption. </para> </message> @@ -52418,11 +52408,10 @@ <message> <para> - Fixed an old bug in concurrent accesses to - <literal>MERGE</literal> tables (even one - <literal>MERGE</literal> table and <literal>MyISAM</literal> - tables), that could have resulted in a crash or hang of the - server. + Concurrent accesses to more than one <literal>MERGE</literal> + table, or to one <literal>MERGE</literal> table and a + <literal>MyISAM</literal> tables, could result in a crash or + hang of the server. </para> </message> @@ -52442,8 +52431,8 @@ <message> <para> - Fixed a bug in the <function role="sql">USER()</function> - function caused by an error in the size of the allocated string. + The <function role="sql">USER()</function> function occasionally + failed due an error in the size of the string allocated to it. </para> </message> @@ -52525,9 +52514,9 @@ <message> <para> - Fixed bug in the MySQL Instance manager that caused the version - to always be <literal>unknown</literal> when <literal>SHOW - INSTANCE STATUS</literal> was issued. + The MySQL Instance manager caused the version to be displayed as + <literal>unknown</literal> by <literal>SHOW INSTANCE + STATUS</literal>. </para> </message> @@ -52622,6 +52611,7 @@ <logentry entrytype="bug"> <tags> + <highlight type="performance"/> <manual type=".ibd"/> <manual type="ibdata"/> <manual type="InnoDB"/> @@ -52634,11 +52624,11 @@ <message> <para> - <literal>InnoDB</literal>: Fix a performance bug: At the - shutdown, write the latest lsn only to the first pages of the - <filename>ibdata</filename> files of the system tablespace, NOT - to the <filename>.ibd</filename> files; writing to tens of - thousands <filename>.ibd</filename> files can take minutes. + <literal>InnoDB</literal>: At shutdown, the latest lsn is now + written only to the first pages of the + <filename>ibdata</filename> files of the system tablespace, and + not to the <filename>.ibd</filename> files, saving up to several + minutes in some cases. </para> </message> @@ -52701,9 +52691,9 @@ <message> <para> - Fixed that <command>mysql-test-run</command> failed on the - <literal>rpl_trunc_binlog</literal> test if running test from - the installed (the target of 'make install') directory. + <command>mysql-test-run</command> failed the + <literal>rpl_trunc_binlog</literal> test when running the test + from the installation directory. </para> </message> @@ -53805,9 +53795,10 @@ <message> <para> - Fixed crash of <function role="sql">GROUP_CONCAT()</function> on - expression with <literal>ORDER BY</literal> and external - <literal>ORDER BY</literal> in a query. + Using the <function role="sql">GROUP_CONCAT()</function> + function on an expression with <literal>ORDER BY</literal> as + well as an external <literal>ORDER BY</literal> in a query + caused the server to crash. </para> </message> @@ -53909,10 +53900,9 @@ <message> <para> - Fixed a bug in multiple-table <literal>UPDATE</literal> - statements that could cause spurious <literal>Table '#sql_....' - is full</literal> errors if the number of rows to update is big - enough. + Multiple-table <literal>UPDATE</literal> statements could cause + spurious <errortext>Table '#sql_....' is full</errortext> errors + if the number of rows to update was sufficiently large. </para> </message> @@ -53960,9 +53950,9 @@ <message> <para> - Fixed <command>mysql</command> parser not to erroneously - interpret <quote> <literal>;</literal> </quote> character within - <literal>/* ... */</literal> comment as statement terminator. + <command>mysql</command> parser erroneously interpreted a + <literal>;</literal> character within a multi-line comment + (<literal>/* ... */</literal>) as a statement terminator. </para> </message> @@ -54045,8 +54035,8 @@ <message> <para> - Fixed an unlikely deadlock which could happen when using - <literal>KILL</literal>. + A deadlock could happen under certain rare circumstances when + using <literal>KILL</literal>. </para> </message> @@ -54127,8 +54117,8 @@ <message> <para> - Fixed <literal>LOAD INDEX</literal> statement to actually load - index in memory. + <literal>LOAD INDEX</literal> statement now loads the index into + memory. </para> </message> @@ -54463,8 +54453,9 @@ <message> <para> - Fixed parsing of short-form IP addresses in - <function role="sql">INET_ATON()</function>. + Short-form IP addresses used as arguments to + <function role="sql">INET_ATON()</function> were not parsed + correctly. </para> </message> @@ -54594,8 +54585,8 @@ <message> <para> - Fixed incorrect memory block allocation for the query cache in - the embedded server. + Memory block allocation did not function correctly for the query + cache in the embedded server. </para> </message> @@ -55213,6 +55204,7 @@ <logentry entrytype="bug"> <tags> + <highlight type="securityfix"/> <manual type="user"/> <manual type="root"/> <manual type="mysqld"/> @@ -55230,11 +55222,10 @@ <message> <para> - <emphasis role="bold">Security fix:</emphasis> If - <command>mysqld</command> was started with - <option>--user=<replaceable>non_existent_user</replaceable> - </option>, it would run using the privileges of the account it - was invoked from, even if that was <literal>root</literal>. + Starting <command>mysqld</command> with + <option>--user=<replaceable>non_existent_user</replaceable></option> + caused it to run using the privileges of the account from which + it was invoked, including the <literal>root</literal> account. </para> </message> @@ -55457,9 +55448,8 @@ <message> <para> - Fixed a bug that caused server crash if some error occurred - during filling of temporary table created for derived table or - view handling. + The server crashed when an error occurred during the filling of + a temporary table created for handling a view or derived table. </para> </message> @@ -55794,9 +55784,9 @@ <message> <para> - Fixed a problem with the <literal>cp1250_czech_cs</literal> - collation that caused empty literal strings not to compare equal - to empty character columns. + When using the <literal>cp1250_czech_cs</literal> collation, + empty literal strings were not regarded as equal to empty + character columns. </para> </message> @@ -55901,8 +55891,8 @@ <message> <para> - Fixed some byte order bugs with prepared statements on machines - with high-byte-first. + Prepared statements did not always work correctly on big-endian + platforms. </para> </message> @@ -56645,9 +56635,8 @@ <message> <para> - Fixed erroneous comparison where strings that began with - <literal>CHAR(31)</literal> were considered equal to the empty - string. + Strings that began with <literal>CHAR(31)</literal> were + considered equal to the empty string. </para> </message> @@ -56726,9 +56715,9 @@ <message> <para> - Fixed bug with wrong result of <function role="sql">CONCAT(?, - <replaceable>col_name</replaceable>)</function> in prepared - statements. + <function role="sql">CONCAT(?, + <replaceable>col_name</replaceable>)</function>, when used in + prepared statements, returned incorrect results. </para> </message> @@ -56842,9 +56831,8 @@ <message> <para> - Fixed that <command>mysql-test-run</command> failed on the - <literal>grant_cache</literal> test when run as Unix user - 'root'. + <command>mysql-test-run</command> failed the + <literal>grant_cache</literal> test when run as Unix root user. </para> </message> @@ -57237,9 +57225,8 @@ <message> <para> - Fixed a server crash resulting from invocation of a stored - function that returned a value having a <literal>BIT</literal> - data type. + Invocation of a stored function that returned a value having a + <literal>BIT</literal> data type caused the server to crash. </para> </message> @@ -57723,11 +57710,9 @@ <message> <para> - <literal>InnoDB</literal>: Fixed a bug: if we dropped a table - where an <literal>INSERT</literal> was waiting for a lock to - check a <literal>FOREIGN KEY</literal> constraint, then an - assertion would fail in - <literal>lock_reset_all_on_table()</literal>. + <literal>InnoDB</literal>: Dropping a table where an + <literal>INSERT</literal> was waiting for a lock to check a + <literal>FOREIGN KEY</literal> constraint caused an assertion. </para> </message> @@ -57747,11 +57732,9 @@ <message> <para> - <literal>InnoDB</literal>: Fix a little bug: we looked at the - physical size of a stored SQL <literal>NULL</literal> value from - a wrong field in the index; this has probably caused no bugs - visible to the user. It caused only some extra space to be used - in some rare cases. + <literal>InnoDB</literal>: The storgae of an SQL + <literal>NULL</literal> value in some rare cases took more space + than should have been required. </para> </message> @@ -57999,8 +57982,8 @@ <message> <para> - Fixed incorrect results of aggregate functions in subquery with - empty result set. + Results of aggregate functions used in subqueries with empty + result sets were incorrect. </para> </message> @@ -58021,11 +58004,10 @@ <message> <para> - Fixed merging types and length of result set columns for - <literal>UNION</literal> operations. The types and lengths now - are determined taking into account values for all - <literal>SELECT</literal> statements in the - <literal>UNION</literal>, not just the first + The types and lengths of result set columns for + <literal>UNION</literal> operations are now determined taking + into account values for all <literal>SELECT</literal> statements + in the <literal>UNION</literal>, and not just the first <literal>SELECT</literal>. </para> @@ -100889,8 +100871,6 @@ </logentry> -<!-- WL#4169 EDITS THROUGH HERE --> - <logentry entrytype="bug"> <bugs>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r11371 - trunk/dynamic-docs/changelog | jon | 25 Jul |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.724 sec. using MySQL 5.1.14-beta-log