svn commit - mysqldoc@docsrva: r5475 - in trunk: . refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2007-03-20 18:47:18 +0100 (Tue, 20 Mar 2007)
New Revision: 5475

Log:
 r21922@polar:  paul | 2007-03-20 12:46:11 -0500
 Document bugfix#27033.


Modified:
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.1/news-5.1.xml

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


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-03-20 17:30:46 UTC (rev 5474)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-03-20 17:47:18 UTC (rev 5475)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 0; 1378 bytes

@@ -79,6 +79,26 @@
 
       <listitem>
         <para>
+          For <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal>
+          statements on tables containing
+          <literal>AUTO_INCREMENT</literal> columns,
+          <literal>LAST_INSERT_ID()</literal> was reset to 0 if no rows
+          were successfully inserted or changed. <quote>Not
+          changed</quote> includes the case where a row was updated to
+          its current values, but in that case,
+          <literal>LAST_INSERT_ID()</literal> should not be reset to 0.
+          Now <literal>LAST_INSERT_ID()</literal> is reset to 0 only if
+          no rows were successfully inserted or touched, whether or not
+          touched rows were changed. (Bug #27033)
+        </para>
+
+        <para>
+          This bug was introduced by the fix for Bug #19978.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           For an <literal>INSERT</literal> statement that should fail
           due to a column with no default value not being assigned a
           value, the statement succeeded with no error if the column was


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-03-20 17:30:46 UTC (rev 5474)
+++ trunk/refman-5.1/news-5.1.xml	2007-03-20 17:47:18 UTC (rev 5475)
Changed blocks: 1, Lines Added: 20, Lines Deleted: 0; 1338 bytes

@@ -282,6 +282,26 @@
 
       <listitem>
         <para>
+          For <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal>
+          statements on tables containing
+          <literal>AUTO_INCREMENT</literal> columns,
+          <literal>LAST_INSERT_ID()</literal> was reset to 0 if no rows
+          were successfully inserted or changed. <quote>Not
+          changed</quote> includes the case where a row was updated to
+          its current values, but in that case,
+          <literal>LAST_INSERT_ID()</literal> should not be reset to 0.
+          Now <literal>LAST_INSERT_ID()</literal> is reset to 0 only if
+          no rows were successfully inserted or touched, whether or not
+          touched rows were changed. (Bug #27033)
+        </para>
+
+        <para>
+          This bug was introduced by the fix for Bug #19978.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>AFTER UPDATE</literal> triggers were not activated if
           a row was not actually changed by the update part of an
           <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal>