| List: | Commits | « Previous MessageNext Message » | |
| From: | paul | Date: | February 3 2007 3:49am |
| Subject: | svn commit - mysqldoc@docsrva: r4775 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | ||
| View as plain text | |||
Author: paul Date: 2007-02-03 03:49:41 +0100 (Sat, 03 Feb 2007) New Revision: 4775 Log: r15835@frost: paul | 2007-02-02 20:47:24 -0600 Document bugfixes: Bug#15518 Bug#17498 Bug#23735 Bug#24085 Bug#24127 Bug#24491 Modified: trunk/refman-4.1/news-4.1.xml trunk/refman-5.0/releasenotes-es-5.0.xml trunk/refman-5.1/news-5.1.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:19331 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:15833 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:19331 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:15835 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520 Modified: trunk/refman-4.1/news-4.1.xml =================================================================== --- trunk/refman-4.1/news-4.1.xml 2007-02-02 23:34:52 UTC (rev 4774) +++ trunk/refman-4.1/news-4.1.xml 2007-02-03 02:49:41 UTC (rev 4775) Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 788 bytes @@ -226,6 +226,15 @@ <listitem> <para> + No warning was issued for use of the <literal>DATA + DIRECTORY</literal> or <literal>INDEX DIRECTORY</literal> + table options on a platform that does not support them. (Bug + #17498) + </para> + </listitem> + + <listitem> + <para> Hebrew-to-Unicode conversion failed for some characters. Definitions for the following Hebrew characters (as specified by the ISO/IEC 8859-8:1999) were added: LEFT-TO-RIGHT MARK Modified: trunk/refman-5.0/releasenotes-es-5.0.xml =================================================================== --- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-02-02 23:34:52 UTC (rev 4774) +++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-02-03 02:49:41 UTC (rev 4775) Changed blocks: 1, Lines Added: 58, Lines Deleted: 0; 2579 bytes @@ -109,6 +109,64 @@ <listitem> <para> + Queries that evaluate <literal>NULL IN (SELECT ... UNION + SELECT ...)</literal> could produce an incorrect result + (<literal>FALSE</literal> instead of <literal>NULL</literal>). + (Bug #24085) + </para> + </listitem> + + <listitem> + <para> + When reading from the standard input on Windows, + <command>mysqlbinlog</command> opened the input in text mode + rather than binary mode and consequently misinterpreted some + characters such as Control-Z. (Bug #23735) + </para> + </listitem> + + <listitem> + <para> + Within stored routines or prepared statements, inconsistent + results occurred with multiple use of <literal>INSERT ... + SELECT ... ON DUPLICATE KEY UPDATE</literal> when the + <literal>ON DUPLICATE KEY UPDATE</literal> clause erroneously + tried to assign a value to a column mentioned only in its + <literal>SELECT</literal> part. (Bug #24491) + </para> + </listitem> + + <listitem> + <para> + Expressions of the form + <literal>(<replaceable>a</replaceable>, + <replaceable>b</replaceable>) IN (SELECT + <replaceable>c</replaceable>, <replaceable>d</replaceable> + ...)</literal> could produce incorrect results if + <replaceable>a</replaceable>, <replaceable>b</replaceable>, or + both are <literal>NULL</literal>. (Bug #24127) + </para> + </listitem> + + <listitem> + <para> + No warning was issued for use of the <literal>DATA + DIRECTORY</literal> or <literal>INDEX DIRECTORY</literal> + table options on a platform that does not support them. (Bug + #17498) + </para> + </listitem> + + <listitem> + <para> + When a prepared statement failed during the prepare operation, + the error code was not cleared when it was reused, even if the + subsequent use was successful. (Bug #15518) + </para> + </listitem> + + <listitem> + <para> <command>mysql_upgrade</command> failed when called with a <literal>basedir</literal> pathname containing spaces. (Bug #22801) Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2007-02-02 23:34:52 UTC (rev 4774) +++ trunk/refman-5.1/news-5.1.xml 2007-02-03 02:49:41 UTC (rev 4775) Changed blocks: 9, Lines Added: 80, Lines Deleted: 31; 6983 bytes @@ -95,42 +95,74 @@ </para> <itemizedlist> - + <listitem> <para> + Queries that evaluate <literal>NULL IN (SELECT ... UNION + SELECT ...)</literal> could produce an incorrect result + (<literal>FALSE</literal> instead of <literal>NULL</literal>). + (Bug #24085) + </para> + </listitem> + + <listitem> + <para> + Within stored routines or prepared statements, inconsistent + results occurred with multiple use of <literal>INSERT ... + SELECT ... ON DUPLICATE KEY UPDATE</literal> when the + <literal>ON DUPLICATE KEY UPDATE</literal> clause erroneously + tried to assign a value to a column mentioned only in its + <literal>SELECT</literal> part. (Bug #24491) + </para> + </listitem> + + <listitem> + <para> + Expressions of the form + <literal>(<replaceable>a</replaceable>, + <replaceable>b</replaceable>) IN (SELECT + <replaceable>c</replaceable>, <replaceable>d</replaceable> + ...)</literal> could produce incorrect results if + <replaceable>a</replaceable>, <replaceable>b</replaceable>, or + both are <literal>NULL</literal>. (Bug #24127) + </para> + </listitem> + + <listitem> + <para> An <literal>AFTER UPDATE</literal> trigger on an <literal>InnoDB</literal> table with a composite primary key caused the server to crash. (Bug#25398) </para> </listitem> - + <listitem> <para> A query that contained an <literal>EXIST</literal> subquery with a <literal>UNION</literal> over correlated and uncorrelated <literal>SELECT</literal> queries could cause the - server to crash. (Bug #25219) + server to crash. (Bug #25219) </para> </listitem> - + <listitem> <para> A query with <literal>ORDER BY</literal> and <literal>GROUP - BY</literal> clauses where the <literal>ORDER BY</literal> + BY</literal> clauses where the <literal>ORDER BY</literal> clause had more elements than the <literal>GROUP BY</literal> clause caused a memory overrun leading to a crash of the server. (Bug #25172) </para> </listitem> - + <listitem> <para> Certain joins using <literal>Range checked for each - record</literal> in the query execution plan could cause the + record</literal> in the query execution plan could cause the server to crash. (Bug #24776) </para> </listitem> - + <listitem> <para> If a prepared statement accessed a view, access to the tables @@ -138,7 +170,7 @@ security context of the view. (Bug #24404) </para> </listitem> - + <listitem> <para> A nested query on a partitioned table returned fewer records @@ -417,6 +449,32 @@ <listitem> <para> + When reading from the standard input on Windows, + <command>mysqlbinlog</command> opened the input in text mode + rather than binary mode and consequently misinterpreted some + characters such as Control-Z. (Bug #23735) + </para> + </listitem> + + <listitem> + <para> + No warning was issued for use of the <literal>DATA + DIRECTORY</literal> or <literal>INDEX DIRECTORY</literal> + table options on a platform that does not support them. (Bug + #17498) + </para> + </listitem> + + <listitem> + <para> + When a prepared statement failed during the prepare operation, + the error code was not cleared when it was reused, even if the + subsequent use was successful. (Bug #15518) + </para> + </listitem> + + <listitem> + <para> <command>mysql_upgrade</command> failed when called with a <literal>basedir</literal> pathname containing spaces. (Bug #22801) @@ -431,7 +489,7 @@ (LRM), RIGHT-TO-LEFT MARK (RLM) (Bug #24037) </para> </listitem> - + <listitem> <para> If there was insufficient memory available to @@ -439,7 +497,7 @@ server to hang during startup. (Bug #24751) </para> </listitem> - + <listitem> <para> Using row-based replication to replicate to a table having at @@ -448,7 +506,7 @@ slave to fail. (Bug #24490) </para> </listitem> - + <listitem> <para> Optimizations that are legal only for subqueries without @@ -456,24 +514,24 @@ for any subquery without tables. (Bug #24670) </para> </listitem> - + <listitem> <para> A query using <literal>WHERE - <replaceable>unsigned_column</replaceable> NOT IN - ('<replaceable>negative_value</replaceable>')</literal> - could cause the server to crash. (Bug #24261) + <replaceable>unsigned_column</replaceable> NOT IN + ('<replaceable>negative_value</replaceable>')</literal> could + cause the server to crash. (Bug #24261) </para> </listitem> - + <listitem> <para> A <literal>FETCH</literal> statement using a cursor on a table which was not in the table cache could sometimes cause the - server to crash. (Bug #24117) + server to crash. (Bug #24117) </para> </listitem> - + <listitem> <para> <literal>CREATE TABLE ... SELECT</literal> statements were not @@ -2257,15 +2315,6 @@ <listitem> <para> - When reading from the standard input on Windows, - <command>mysqlbinlog</command> opened the input in text mode - rather than binary mode and consequently misinterpreted some - characters such as Control-Z. (Bug #23735) - </para> - </listitem> - - <listitem> - <para> Inserting a default or invalid value into a spatial column could fail with <literal>Unknown error</literal> rather than a more appropriate error. (Bug #21790) @@ -4210,15 +4259,15 @@ REPAIR TABLE <replaceable>tbl_name</replaceable> QUICK; </programlisting> </listitem> - + <listitem> <para> An invalid <literal>GRANT</literal> statement for which <literal>Ok</literal> was returned on a replication master caused an error on the slave and replication to fail. (Bug - #6774) + #6774) </para> - </listitem> + </listitem> <listitem> <para>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r4775 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 3 Feb |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.489 sec. using MySQL 5.1.14-beta-log