List:Commits« Previous MessageNext Message »
From:paul.dubois Date:October 7 2008 8:14pm
Subject:svn commit - mysqldoc@docsrva: r12009 - in trunk: . dynamic-docs/changelog
View as plain text  
Author: paul
Date: 2008-10-07 22:14:36 +0200 (Tue, 07 Oct 2008)
New Revision: 12009

Log:
 r34617@frost:  paul | 2008-10-07 15:07:33 -0500
 Document 5.1.29 bugfixes:
 Bug#26020: User-Defined Variables are not consistence with columns data types
 Bug#35981: ALTER EVENT causes the server to change the PRESERVE option.
 Bug#37949: Crash if argument to SP is a subquery that returns more than one row
 Bug#38083: Error-causing row inserted into partitioned table despite error
 Bug#38360: BLACKHOLE replication with RBR is broken
 Bug#39182: Binary log producing incompatible character set query from stored procedure.
 Bug#39353: Multiple conditions on timestamp column crashes server


Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:34615
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:34617
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-10-07 19:22:17 UTC (rev 12008)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-10-07 20:14:36 UTC (rev 12009)
Changed blocks: 1, Lines Added: 184, Lines Deleted: 0; 3732 bytes

@@ -29591,4 +29591,188 @@
 
   </logentry>
 
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="ALTER EVENT"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="35981"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.29"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal>ALTER EVENT</literal> changed the
+        <literal>PRESERVE</literal> attribute of an event even when
+        <literal>PRESERVE</literal> was not specified in the statement.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="stored procedures"/>
+      <manual type="subqueries"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="37949"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.29"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The server crashed if an argument to a stored procedure was a
+        subquery that returned more than one row.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="NAME_CONST()"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39182"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.29"/>
+    </versions>
+
+    <message>
+
+      <para>
+        References to local variables in stored procedures are replaced
+        with
+        <function role="sql">NAME_CONST(<replaceable>name</replaceable>,
+        <replaceable>value</replaceable>)</function> when written to the
+        binary log. However, an <quote>illegal mix of collation</quote>
+        error might occur when executing the log contents if the value's
+        collation differed from that of the variable. Now information
+        about the variable collation is written as well.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="partitions"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="38083"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.29"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If an error occurred when evaluating a column of a partitioned
+        table for the partitioning function, the row could be inserted
+        anyway.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="BLACKHOLE"/>
+      <manual type="replication"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="38360"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.29"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Replication of <literal>BLACKHOLE</literal> tables did not work
+        with row-based binary logging.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="InnoDB"/>
+      <manual type="TIMESTAMP"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39353"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.29"/>
+    </versions>
+
+    <message>
+
+      <para>
+        For a <literal>TIMESTAMP</literal> column in an
+        <literal>InnoDB</literal> table, testing the column with
+        multiple conditions in the <literal>WHERE</literal> clause
+        caused a server crash.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="26020"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.29"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The server could improperly type user-defined variables used in
+        the select list of a query.
+      </para>
+
+    </message>
+
+  </logentry>
+
 </changelog>


Thread
svn commit - mysqldoc@docsrva: r12009 - in trunk: . dynamic-docs/changelogpaul.dubois7 Oct