| List: | Internals | « Previous MessageNext Message » | |
| From: | paul | Date: | November 20 2005 6:04am |
| Subject: | svn commit - mysqldoc@docsrva: r370 - in trunk: . refman-common | ||
| View as plain text | |||
Author: paul Date: 2005-11-20 06:04:21 +0100 (Sun, 20 Nov 2005) New Revision: 370 Log: r3921@frost: paul | 2005-11-19 23:03:56 -0600 Document bugfixes: Bug#9551 Bug#13627 Bug#13399 Bug#12329 Bug#14397 Bug#14342 Bug#13707 Bug#14723 Bug#14569 Bug#14616 Bug#13806 Bug#14845 Bug#14433 Bug#14719 Bug#11796 Bug#14469 Bug#13632 Bug#13622 Bug#14480 Bug#14631 Modified: trunk/ trunk/refman-common/news-4.0.xml trunk/refman-common/news-4.1.xml trunk/refman-common/news-5.0.xml trunk/refman-common/news-connector-net.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3920 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1101 + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3921 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1101 Modified: trunk/refman-common/news-4.0.xml =================================================================== --- trunk/refman-common/news-4.0.xml 2005-11-20 05:04:09 UTC (rev 369) +++ trunk/refman-common/news-4.0.xml 2005-11-20 05:04:21 UTC (rev 370) @@ -176,6 +176,24 @@ <listitem> <para> + A <literal>LIMIT</literal>-related optimization failed to take + into account that <literal>MyISAM</literal> table indexes can + be disabled, causing Error 124 when it tried to use such an + index. (Bug #14616) + </para> + </listitem> + + <listitem> + <para> + For a table that had been opened with <literal>HANDLER + OPEN</literal>, issuing <literal>OPTIMIZE TABLE</literal>, + <literal>ALTER TABLE</literal>, or <literal>REPAIR + TABLE</literal> caused a server crash. (Bug #14397) + </para> + </listitem> + + <listitem> + <para> Queries of the form <literal>(SELECT ...) ORDER BY ...</literal> were being treated as a <literal>UNION</literal>. This improperly resulted in only Modified: trunk/refman-common/news-4.1.xml =================================================================== --- trunk/refman-common/news-4.1.xml 2005-11-20 05:04:09 UTC (rev 369) +++ trunk/refman-common/news-4.1.xml 2005-11-20 05:04:21 UTC (rev 370) @@ -246,12 +246,47 @@ <listitem> <para> + <filename>mysql_fix_privilege_tables.sql</filename> contained + an erroneous comment that resulted in an error when the file + contents were processed. (Bug #14469) + </para> + </listitem> + + <listitem> + <para> + On Windows, the server could crash during shutdown if both + replication threads and normal client connection threads were + active. (Re-fix of Bug #11796) + </para> + </listitem> + + <listitem> + <para> + A <literal>LIMIT</literal>-related optimization failed to take + into account that <literal>MyISAM</literal> table indexes can + be disabled, causing Error 124 when it tried to use such an + index. (Bug #14616) + </para> + </listitem> + + <listitem> + <para> + For a table that had been opened with <literal>HANDLER + OPEN</literal>, issuing <literal>OPTIMIZE TABLE</literal>, + <literal>ALTER TABLE</literal>, or <literal>REPAIR + TABLE</literal> caused a server crash. (Bug #14397) + </para> + </listitem> + + <listitem> + <para> <literal>CREATE TABLE <replaceable>tbl_name</replaceable> (…) SELECT …</literal> could crash the server and write invalid data into the <filename>.frm</filename> file if the <literal>CREATE TABLE</literal> and <literal>SELECT</literal> both contained a column with the - same name. (Bug #14480) + same name. Also, if a default value is specified in the column + definition, it is now actually used. (Bug #14480) </para> </listitem> Modified: trunk/refman-common/news-5.0.xml =================================================================== --- trunk/refman-common/news-5.0.xml 2005-11-20 05:04:09 UTC (rev 369) +++ trunk/refman-common/news-5.0.xml 2005-11-20 05:04:21 UTC (rev 370) @@ -186,10 +186,140 @@ Bugs fixed: </para> - <remark role="note"> - Replace with itemized list when there are items to place here. - </remark> + <itemizedlist> + <listitem> + <para> + <literal>CREATE TABLE <replaceable>tbl_name</replaceable> + (…) SELECT …</literal> could crash the server + and write invalid data into the <filename>.frm</filename> file + if the <literal>CREATE TABLE</literal> and + <literal>SELECT</literal> both contained a column with the + same name. Also, if a default value is specified in the column + definition, it is now actually used. (Bug #14480) + </para> + </listitem> + + <listitem> + <para> + A newline character in a column alias in a view definition + caused an error when selecting from the view later. (Bug + #13622) + </para> + </listitem> + + <listitem> + <para> + <filename>mysql_fix_privilege_tables.sql</filename> contained + an erroneous comment that resulted in an error when the file + contents were processed. (Bug #14469) + </para> + </listitem> + + <listitem> + <para> + On Windows, the server could crash during shutdown if both + replication threads and normal client connection threads were + active. (Re-fix of Bug #11796) + </para> + </listitem> + + <listitem> + <para> + The grammar for supporting the <literal>DEFINER = + CURRENT_USER</literal> clause in <literal>CREATE + VIEW</literal> and <literal>ALTER VIEW</literal> was + incorrect. (Bug #14719) + </para> + </listitem> + + <listitem> + <para> + Queries on <literal>ARCHIVE</literal> tables that used the + <literal>filesort</literal> sorting method could result in a + server crash. (Bug #14433) + </para> + </listitem> + + <listitem> + <para> + The <literal>mysql_stmt_fetch()</literal> C APP function could + return <literal>MYSQL_NO_DATA</literal> for a <literal>SELECT + COUNT(*) FROM <replaceable>tbl_name</replaceable> WHERE 1 = + 0</literal> statement, which should return 1 row. (Bug #14845) + </para> + </listitem> + + <listitem> + <para> + A <literal>LIMIT</literal>-related optimization failed to take + into account that <literal>MyISAM</literal> table indexes can + be disabled, causing Error 124 when it tried to use such an + index. (Bug #14616) + </para> + </listitem> + + <listitem> + <para> + A server crash resulted from the following sequence of events: + 1) With no default database selected, create a stored + procedure with the procedure name explicitly qualified with a + database name (<literal>CREATE PROCEDURE + <replaceable>db_name</replaceable>.<replaceable>proc_name</replaceable> + …</literal>). 2) Create another stored procedure with + no database name qualifier. 3) Execute <literal>SHOW PROCEDURE + STATUS</literal>. (Bug #14569) + </para> + </listitem> + + <listitem> + <para> + Complex subqueries could cause improper internal query + execution environment initialization and crash the server. + (Bug #14342) + </para> + </listitem> + + <listitem> + <para> + For a table that had been opened with <literal>HANDLER + OPEN</literal>, issuing <literal>OPTIMIZE TABLE</literal>, + <literal>ALTER TABLE</literal>, or <literal>REPAIR + TABLE</literal> caused a server crash. (Bug #14397) + </para> + </listitem> + + <listitem> + <para> + A server crash could occur if a prepared statement invoked a + stored procedure that existed when the statement was prepared + but had been dropped and recreated prior to statement + execution. (Bug #12329) + </para> + </listitem> + + <listitem> + <para> + A server crash could occur if a prepared statement updated a + table for which a trigger existed when the statement was + prepared but had been dropped prior to statement execution. + (Bug #13399) + </para> + </listitem> + + <listitem> + <para> + Statements that implicitly commit a transaction are prohibited + in stored functions and triggers. An attempt to create a + function or trigger containing such a statement produces an + error. (Bug #13627) (The originally reported symptom was that + a trigger that dropped another trigger could cause a server + crash. That problem was fixed by the patch for Bug #13343.) + </para> + </listitem> + + </itemizedlist> + </section> <section id="news-5-0-16"> @@ -275,6 +405,32 @@ <listitem> <para> + For some stored functions dumped by <command>mysqldump + --routines</command>, the function definition could not be + reloaded later due to a parsing error. (Bug #14723) + </para> + </listitem> + + <listitem> + <para> + For a <literal>MyISAM</literal> table originally created in + MySQL 4.1, <literal>INSERT DELAYED</literal> could cause a + server crash. (Bug #13707) + </para> + </listitem> + + <listitem> + <para> + The <option>--exit-info=65536</option> option conflicted with + <option>--temp-pool</option> and caused problems with the + server's use of temporary files. Now + <option>--temp-pool</option> is ignored if + <option>--exit-info=65536</option> is specified. (Bug #9551) + </para> + </listitem> + + <listitem> + <para> <literal>ORDER BY DESC</literal> within the <literal>GROUP_CONCAT()</literal> function was not honored when used in a view. (Bug #14466) @@ -924,6 +1080,10 @@ </listitem> </itemizedlist> + + <para> + (Bug #13343) + </para> </listitem> <listitem> @@ -3061,7 +3221,7 @@ <listitem> <para> Column names in subqueries must be unique, but were not being - checked for uniqueness. (Bug #11796) + checked for uniqueness. (Bug #11864) </para> </listitem> Modified: trunk/refman-common/news-connector-net.xml =================================================================== --- trunk/refman-common/news-connector-net.xml 2005-11-20 05:04:09 UTC (rev 369) +++ trunk/refman-common/news-connector-net.xml 2005-11-20 05:04:21 UTC (rev 370) @@ -1,5 +1,5 @@ <?xml version='1.0' encoding='utf-8'?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ <!ENTITY % fixedchars.entities SYSTEM "fixedchars.ent"> @@ -46,6 +46,31 @@ <listitem> <para> + A <literal>#42000Query was empty</literal> exception occurred + when executing a query built with + <literal>MySqlCommandBuilder</literal>, if the query string + ended with a semicolon. (Bug #14631) + </para> + </listitem> + + <listitem> + <para> + Implemented the + <literal>MySqlCommandBuilder.DeriveParameters</literal> method + that is used to discover the parameters for a stored + procedure. (Bug #13632) + </para> + </listitem> + + <listitem> + <para> + Added support for the <literal>cp932</literal> character set. + (Bug #13806) + </para> + </listitem> + + <listitem> + <para> Calling a stored procedure where a parameter contained special characters (such as <literal>'@'</literal>) would produce an exception. Note that <literal>ANSI_QUOTES</literal> had to be
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r370 - in trunk: . refman-common | paul | 20 Nov |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.447 sec. using MySQL 5.1.14-beta-log