svn commit - mysqldoc@docsrva: r6546 - trunk/falcon

[mcbrown]

Author: mcbrown
Date: 2007-05-20 07:33:48 +0200 (Sun, 20 May 2007)
New Revision: 6546

Log:
Documenting Dev Bugs: 

Bug #22169
Bug #22847
Bug #23689
Bug #24858
Bug #24068
Bug #24921 
Bug #26057
Bug #26433
Bug #27697



Modified:
   trunk/falcon/news-falcon.xml


Modified: trunk/falcon/news-falcon.xml
===================================================================
--- trunk/falcon/news-falcon.xml	2007-05-19 23:37:43 UTC (rev 6545)
+++ trunk/falcon/news-falcon.xml	2007-05-20 05:33:48 UTC (rev 6546)
Changed blocks: 1, Lines Added: 66, Lines Deleted: 1; 2121 bytes

@@ -18,8 +18,73 @@
     </para>
   </note>
 
-  <section>
+  <section id="news-falcon-6-0-1">
 
+    <title>Changes in release 6.0.1 (Not yet released)</title>
+
+    <para>
+      Bugs fixed:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Searching for rows within a table with some non-western
+          character sets would fail to return the right results if the
+          <literal>SELECT</literal> relied on an index. (Bug #27697)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Searches for accented characters in a UTF8 table fail if an
+          index exists for the column. (Bug #26057)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Searches using <literal>LIKE</literal> on a UTF8 table fail if
+          the search relies an indexed column. (Bug #24921)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Searches for data on a partial index for a column using the
+          UTF8 character set would fail. (Bug #24858)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Searches for data using exotic collation/character sets fail
+          if the search relies on an indexed column. (Bug #23689)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Inserting rows to a table with a unique index where the unique
+          index value is identical on two separate connections would
+          block the second transaction. (Bug #22847)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Large inserts to a table within a single transaction trigger
+          high memory usage and may ultimately crash. (Bug #22169)
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </section>
+
+  <section id="news-falcon-6-0-0">
+
     <title>Changes in release 6.0.0 (30 April 2007)</title>
 
     <para>