Author: paul
Date: 2009-09-10 19:30:27 +0200 (Thu, 10 Sep 2009)
New Revision: 16553
Log:
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:26218
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:44393
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
+ 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:26218
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:44396
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-09-10 16:36:03 UTC (rev 16552)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-09-10 17:30:27 UTC (rev 16553)
Changed blocks: 1, Lines Added: 67, Lines Deleted: 0; 2722 bytes
@@ -9,6 +9,73 @@
<logentry entrytype="bug">
<tags>
+ <highlight type="replication"/>
+ <manual type="CREATE ... IF NOT EXISTS"/>
+ <manual type="binlog"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="45574"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.39"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The binary logging behavior (and thus, the replication behavior)
+ of <literal role="stmt" condition="create-database">CREATE
+ DATABASE IF NOT EXISTS</literal>,
+ <literal role="stmt" condition="create-table">CREATE TABLE IF
+ NOT EXISTS</literal>, and
+ <literal role="stmt" condition="create-event">CREATE EVENT IF
+ NOT EXISTS</literal> was not consistent among these statements,
+ nor with that of
+ <literal role="stmt" condition="drop-database">DROP DATABASE IF
+ EXISTS</literal>,
+ <literal role="stmt" condition="drop-table">DROP TABLE IF
+ EXISTS</literal>, and
+ <literal role="stmt" condition="drop-event">DROP EVENT IF
+ EXISTS</literal>: A <literal>DROP ... IF EXISTS</literal>
+ statement is always logged even if the database object named in
+ the statement does not exist. However, of the <literal>CREATE
+ ... IF NOT EXISTS</literal> statements, only the
+ <literal role="stmt" condition="create-event">CREATE EVENT IF
+ NOT EXISTS</literal> statement was logged when the database
+ object named in the statement already existed.
+ </para>
+
+ <para>
+ Now, every <literal>CREATE ... IF NOT EXISTS</literal> statement
+ is written to the binary log (and thus replicated), whether the
+ database object named in the statement exists or not. For more
+ information, see
+ <xref linkend="replication-features-create-if-not-exists"/>.
+ </para>
+
+ <formalpara>
+
+ <title>Exception</title>
+ <para>
+ Replication and logging of
+ <literal role="stmt" condition="create-table">CREATE TABLE IF
+ NOT EXISTS ... SELECT</literal> continues to be handled
+ according to existing rules. See
+ <xref linkend="replication-features-create-select"/>, for more
+ information.
+ </para>
+
+ </formalpara>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
<highlight type="cluster"/>
<manual type="Mac OS X"/>
<manual type="ndb_mgm"/>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r16553 - in trunk: . dynamic-docs/changelog | paul.dubois | 10 Sep |