svn commit - mysqldoc@docsrva: r23504 - trunk/dynamic-docs/changelog

[jon.stephens]

Author: jstephens
Date: 2010-11-01 13:47:47 +0100 (Mon, 01 Nov 2010)
New Revision: 23504

Log:



Changelog entry for Replication BUG#55478





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


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-11-01 11:15:13 UTC (rev 23503)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-11-01 12:47:47 UTC (rev 23504)
Changed blocks: 1, Lines Added: 62, Lines Deleted: 0; 2485 bytes

@@ -10,6 +10,68 @@
 
     <tags>
       <highlight type="replication"/>
+      <manual type="temporary tables"/>
+      <manual type="CREATE TABLE ... SELECT"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="55478"/>
+      <seealsobug bugid="47899"/>
+      <seealsobug bugid="55709"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.53"/>
+      <version ver="5.5.8"/>
+    </versions>
+
+    <message ver="5.1.53">
+
+      <para>
+        If there exist both a temporary table and a non-temporary table
+        having the same, updates normally apply only to the temporary
+        table, with the exception of a
+        <literal role="stmt" condition="create-table-select">CREATE
+        TABLE ... SELECT</literal> statement that creates a
+        non-temporary table having the same name as an existing
+        temporary table. When such a statement was replicated using the
+        <literal>MIXED</literal> logging format, and the statement was
+        unsafe for row-based logging, updates were misapplied to the
+        temporary table.
+      </para>
+
+    </message>
+
+    <message ver="5.5.8">
+
+      <para>
+        If there exist both a temporary table and a non-temporary table
+        having the same, updates normally apply only to the temporary
+        table, with the exception of a
+        <literal role="stmt" condition="create-table-select">CREATE
+        TABLE ... SELECT</literal> statement that creates a
+        non-temporary table having the same name as an existing
+        temporary table. When such a statement was replicated using the
+        <literal>MIXED</literal> logging format, and the statement was
+        unsafe for row-based logging, updates were misapplied to the
+        temporary table.
+      </para>
+
+      <para>
+        Updates were also applied wrongly when a temporary table that
+        used a transactional storage engine was dropped inside a
+        transaction, followed by updates within the same transaction to
+        a non-temporary table having the same name.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="replication"/>
       <manual type="ALTER TABLE"/>
       <manual type="binary log"/>
     </tags>