Author: paul
Date: 2007-03-19 22:19:52 +0100 (Mon, 19 Mar 2007)
New Revision: 5466
Log:
Revert previous change.
Modified:
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-19 20:09:30 UTC (rev 5465)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-19 21:19:52 UTC (rev 5466)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 28; 1867 bytes
@@ -79,19 +79,6 @@
<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>
- statement. (Bug #27006)
- </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
@@ -156,14 +143,6 @@
applied since the last MySQL Enterprise Server release (5.0.36).
</para>
- <note>
- <para>
- After release, a trigger failure problem was found to have been
- introduced. (Bug #27006) Users affected by this issue should
- upgrade to MySQL 5.1.17, which corrects the problem.
- </para>
- </note>
-
<para>
Functionality added or changed:
</para>
@@ -826,13 +805,10 @@
applied since the last MySQL Enterprise Server release (5.0.34).
</para>
- <note>
- <para>
- After release, a trigger failure problem was found to have been
- introduced. (Bug #27006) Users affected by this issue should
- upgrade to MySQL 5.1.17, which corrects the problem.
- </para>
- </note>
+ <remark>
+ Uncomment when there are functionality/feature changes to
+ document.
+ </remark>
<para>
Functionality added or changed:
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-03-19 20:09:30 UTC (rev 5465)
+++ trunk/refman-5.1/news-5.1.xml 2007-03-19 21:19:52 UTC (rev 5466)
Changed blocks: 3, Lines Added: 11, Lines Deleted: 20; 1768 bytes
@@ -68,6 +68,11 @@
<ulink url="http://www.mysql.com/network/advisors.html"/>.
</para>
+ <remark role="TODO">
+ [js] Uncomment following when there are functionality changes or
+ additions to document.
+ </remark>
+
<para>
Functionality added or changed:
</para>
@@ -282,19 +287,6 @@
<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>
- statement. (Bug #27006)
- </para>
-
- <para>
- This bug was introduced by the fix for Bug #19978.
- </para>
- </listitem>
-
- <listitem>
- <para>
For <literal>INSERT ... ON DUPLICATE KEY UPDATE</literal>
statements where some <literal>AUTO_INCREMENT</literal> values
were generated automatically for inserts and some rows were
@@ -970,13 +962,12 @@
for more details about the individual bugs fixed in this version.
</para>
- <note>
- <para>
- After release, a trigger failure problem was found to have been
- introduced. (Bug #27006) Users affected by this issue should
- upgrade to MySQL 5.1.17, which corrects the problem.
- </para>
- </note>
+ <para role="release-special-announcement">
+ <remark>
+ 5. REMOVE WHOLE PARAGRAPH IF THERE IS NOTHING SPECIAL TO
+ ANNOUNCE.
+ </remark>
+ </para>
&enterprise-offering-note;
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5466 - in trunk: refman-5.0 refman-5.1 | paul | 19 Mar |