Author: paul
Date: 2008-01-25 22:46:54 +0100 (Fri, 25 Jan 2008)
New Revision: 9637
Log:
r23408@arctic: paul | 2008-01-25 15:45:08 -0600
Fix bad merge.
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34985
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28742
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:23383
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34985
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:28742
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:23408
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-01-25 21:43:52 UTC (rev 9636)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-01-25 21:46:54 UTC (rev 9637)
Changed blocks: 10, Lines Added: 56, Lines Deleted: 126; 8146 bytes
@@ -5786,42 +5786,16 @@
<logentry entrytype="bug">
<tags>
+ <manual type="UDF"/>
<manual type="optimizer"/>
</tags>
<bugs>
- <fixes bugid="30363"/>
+ <fixes bugid="30355"/>
</bugs>
<versions>
- <version ver="6.0.4"/>
- </versions>
-
- <message>
-
- <para>
- Compared to MySQL 5.1, the 6.0 optimizer failed to use join
- buffering for certain queries, resulting in slower performance
- for those queries.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="filesort"/>
- <manual type="subqueries"/>
- </tags>
-
- <bugs>
- <fixes bugid="33675"/>
- </bugs>
-
- <versions>
- <version ver="5.0.56"/>
+ <version ver="5.0.54"/>
<version ver="5.1.23"/>
<version ver="6.0.5"/>
</versions>
@@ -5829,8 +5803,9 @@
<message>
<para>
- Use of uninitialized memory for <literal>filesort</literal> in a
- subquery caused a server crash.
+ The optimizer made incorrect assumptions about the value of the
+ <literal>is_member</literal> value for user-defined functions,
+ sometimes resulting in incorrect ordering of UDF results.
</para>
</message>
@@ -5840,16 +5815,17 @@
<logentry entrytype="bug">
<tags>
- <manual type="parser"/>
- <manual type="subqueries"/>
+ <manual type="BLACKHOLE"/>
+ <manual type="ALTER TABLE"/>
+ <manual type="locking"/>
</tags>
<bugs>
- <fixes bugid="31797"/>
+ <fixes bugid="30294"/>
</bugs>
<versions>
- <version ver="5.0.56"/>
+ <version ver="5.0.54"/>
<version ver="5.1.23"/>
<version ver="6.0.5"/>
</versions>
@@ -5857,12 +5833,9 @@
<message>
<para>
- Name resolution for correlated subqueries and
- <literal>HAVING</literal> clauses failed to distinguish which of
- two was being performed when there was a reference to an outer
- aliased field. This could result in error messages about a
- <literal>HAVING</literal> clause for queries that had no such
- clause.
+ Simultaneous <literal>ALTER TABLE</literal> statements for
+ <literal>BLACKHOLE</literal> tables caused 100% CPU use due to
+ locking problems.
</para>
</message>
@@ -5872,25 +5845,25 @@
<logentry entrytype="bug">
<tags>
- <manual type="query cache"/>
+ <manual type="DROP DATABASE"/>
</tags>
<bugs>
- <fixes bugid="30887"/>
+ <fixes bugid="30152"/>
</bugs>
<versions>
- <version ver="5.1.24"/>
+ <version ver="5.1.23"/>
<version ver="6.0.5"/>
</versions>
<message>
<para>
- Resetting the query cache by issuing a <literal>SET GLOBAL
- query_cache_size=0</literal> statement caused the server to
- crash if it concurrently was saving a new result set to the
- query cache.
+ If the server crashed during an <literal>ALTER TABLE</literal>
+ statement, leaving a temporary file in the database directory, a
+ subsequent <literal>DROP DATABASE</literal> statement failed due
+ to the presence of the temporary file.
</para>
</message>
@@ -5900,24 +5873,26 @@
<logentry entrytype="bug">
<tags>
- <manual type="enable-pstack"/>
+ <manual type="libmysqld"/>
+ <manual type="mysql_insert_id()"/>
</tags>
<bugs>
- <fixes bugid="29836"/>
+ <fixes bugid="26921"/>
</bugs>
<versions>
- <version ver="5.1.24"/>
+ <version ver="5.1.23"/>
<version ver="6.0.5"/>
</versions>
<message>
<para>
- <command>mysqld</command> displayed the
- <option>--enable-pstack</option> option in its help message even
- if MySQL was configured without <option>--with-pstack</option>.
+ The <function role="capi">mysql_insert_id()</function> C API
+ function sometimes returned different results for
+ <literal>libmysqld</literal> and
+ <literal>libmysqlclient</literal>.
</para>
</message>
@@ -5927,53 +5902,31 @@
<logentry entrytype="bug">
<tags>
- <manual type="stored routines"/>
+ <manual type="mysql_insert_id()"/>
</tags>
<bugs>
- <fixes bugid="33618"/>
+ <fixes bugid="9481"/>
</bugs>
<versions>
- <version ver="5.0.56"/>
- <version ver="5.1.24"/>
- <version ver="6.0.5"/>
+ <version ver="5.0.54"/>
</versions>
<message>
<para>
- The server could crash when <literal>REPEAT</literal> or another
- control instruction was used in conjunction with labels and a
- <literal>LEAVE</literal> instruction.
+ If an <literal>INSERT ... SELECT</literal> statement is
+ executed, and no automatically generated value is successfully
+ inserted, then
+ <function role="capi">mysql_insert_id()</function> returns the
+ ID of the last inserted row.
</para>
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="compound statements"/>
- <manual type="labels"/>
- </tags>
-
- <bugs>
- <fixes bugid="33618"/>
- </bugs>
-
- <versions>
- <version ver="5.0.56"/>
- <version ver="5.1.24"/>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
<para>
- The parser allowed control structures in compound statements to
- have mismatched beginning and ending labels.
+ If no automatically generated value is successfully inserted,
+ then <function role="capi">mysql_insert_id()</function> returns
+ 0.
</para>
</message>
@@ -5983,42 +5936,15 @@
<logentry entrytype="bug">
<tags>
- <manual type="DOUBLE"/>
+ <manual type="CREATE TABLE"/>
</tags>
<bugs>
- <fixes bugid="21497"/>
+ <fixes bugid="33256"/>
</bugs>
<versions>
- <version ver="6.0.5"/>
- </versions>
-
- <message>
-
- <para>
- When inserting an extraordinarly large value into a
- <literal>DOUBLE</literal> column, the value could be truncated
- in such a way that the new value cannot be reloaded manually or
- from the output of <command>mysqldump</command>.
- </para>
-
- </message>
-
- </logentry>
-
- <logentry entrytype="bug">
-
- <tags>
- <manual type="math"/>
- </tags>
-
- <bugs>
- <fixes bugid="12860"/>
- </bugs>
-
- <versions>
- <version ver="5.0.54"/>
+ <version ver="5.0.56"/>
<version ver="5.1.23"/>
<version ver="6.0.5"/>
</versions>
@@ -6026,8 +5952,9 @@
<message>
<para>
- Zero-padding of exponent values was not the same across
- platforms.
+ <literal>CREATE TABLE ... SELECT</literal> created tables that
+ for date columns used the obsolete <literal>Field_date</literal>
+ type instead of <literal>Field_newdate</literal>.
</para>
</message>
@@ -6037,25 +5964,28 @@
<logentry entrytype="bug">
<tags>
- <manual type="math"/>
+ <manual type="subquery"/>
+ <manual type="optimizer"/>
</tags>
<bugs>
- <fixes bugid="24541"/>
+ <fixes bugid="33794"/>
</bugs>
<versions>
+ <version ver="5.0.56"/>
+ <version ver="5.1.24"/>
<version ver="6.0.5"/>
</versions>
<message>
<para>
- <literal>Data truncated for column
- <replaceable>col_num</replaceable> at row
- <replaceable>row_num</replaceable></literal> warnings were
- generated for some (constant) values that did not have too high
- precision.
+ The server crashed when executing a query that had a subquery
+ containing an equality X=Y where Y referred to a named select
+ list expression from the parent select. The server crashed when
+ trying to use the X=Y equality for <literal>ref</literal>-based
+ access.
</para>
</message>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9637 - in trunk: . dynamic-docs/changelog | paul | 25 Jan |
