Author: mcbrown
Date: 2006-07-11 11:21:51 +0200 (Tue, 11 Jul 2006)
New Revision: 2697
Log:
Documenting Dev bug #19835, #14400
Modified:
trunk/refman-common/news-4.0.xml
trunk/refman-common/news-4.1.xml
trunk/refman-common/news-5.0.xml
trunk/refman-common/news-5.1.xml
Modified: trunk/refman-common/news-4.0.xml
===================================================================
--- trunk/refman-common/news-4.0.xml 2006-07-11 08:33:21 UTC (rev 2696)
+++ trunk/refman-common/news-4.0.xml 2006-07-11 09:21:51 UTC (rev 2697)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 730 bytes
@@ -173,6 +173,14 @@
<listitem>
<para>
+ Using <literal>SELECT</literal> and a table join while running
+ a concurrent <literal>INSERT</literal> operation would join
+ incorrect rows. (Bug #14400)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A query with a <literal>WHERE</literal> clause containing
<literal><replaceable>column</replaceable> =
ELT(<replaceable>int_value_1</replaceable>,
Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml 2006-07-11 08:33:21 UTC (rev 2696)
+++ trunk/refman-common/news-4.1.xml 2006-07-11 09:21:51 UTC (rev 2697)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 937 bytes
@@ -223,6 +223,21 @@
<listitem>
<para>
+ Using <literal>SELECT</literal> and a table join while running
+ a concurrent <literal>INSERT</literal> operation would join
+ incorrect rows. (Bug #14400)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>SELECT</literal> on a corrupt table using the
+ dynamic record format could cause a server crash. (Bug #19835)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Checking a spatial table (using <literal>CHECK
TABLE</literal>) with an index and only one row would indicate
a table corruption. (Bug #17877)
Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml 2006-07-11 08:33:21 UTC (rev 2696)
+++ trunk/refman-common/news-5.0.xml 2006-07-11 09:21:51 UTC (rev 2697)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 967 bytes
@@ -304,6 +304,21 @@
<listitem>
<para>
+ Using <literal>SELECT</literal> and a table join while running
+ a concurrent <literal>INSERT</literal> operation would join
+ incorrect rows. (Bug #14400)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>SELECT</literal> on a corrupt table using the
+ dynamic record format could cause a server crash. (Bug #19835)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using tables from MySQL 4.x in MySQL 5.x, in particular those
with <literal>VARCHAR</literal> fields and using
<literal>INSERT DELAYED</literal> to update data in the table
Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml 2006-07-11 08:33:21 UTC (rev 2696)
+++ trunk/refman-common/news-5.1.xml 2006-07-11 09:21:51 UTC (rev 2697)
Changed blocks: 1, Lines Added: 15, Lines Deleted: 0; 937 bytes
@@ -324,6 +324,21 @@
<listitem>
<para>
+ Using <literal>SELECT</literal> and a table join while running
+ a concurrent <literal>INSERT</literal> operation would join
+ incorrect rows. (Bug #14400)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>SELECT</literal> on a corrupt table using the
+ dynamic record format could cause a server crash. (Bug #19835)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Checking a spatial table (using <literal>CHECK
TABLE</literal>) with an index and only one row would indicate
a table corruption. (Bug #17877)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2697 - trunk/refman-common | mcbrown | 11 Jul |
