svn commit - mysqldoc@docsrva: r1787 - in trunk: . refman-common

[paul]

Author: paul
Date: 2006-04-11 05:44:31 +0200 (Tue, 11 Apr 2006)
New Revision: 1787

Log:
 r9366@frost:  paul | 2006-04-10 22:41:16 -0500
 Post-merge fixes.


Modified:
   trunk/
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-5.1.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9365
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6548
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9366
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4334

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-04-11 03:43:51 UTC (rev 1786)
+++ trunk/refman-common/news-5.0.xml	2006-04-11 03:44:31 UTC (rev 1787)
@@ -426,48 +426,12 @@
       <listitem>
         <para>
           The <literal>mysql_close()</literal> C API function leaked
-          handles for share-memory connections on Windows. (Bug #15846)
+          handles for shared-memory connections on Windows. (Bug #15846)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          If <literal>InnoDB</literal> ran out of buffer space for row
-          locks and adaptive hashes, the server would crash. Now
-          <literal>InnoDB</literal> rolls back the transaction. (Bug
-          #18238)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <literal>InnoDB</literal> tables with an adaptive hash blocked
-          other queries during <literal>CHECK TABLE</literal> statements
-          while the entire hash was checked. This could be a long time
-          for a large hash. (Bug #17126)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          For <literal>InnoDB</literal> tables created in MySQL 4.1 or
-          earlier, or created in 5.0 or later with compact format,
-          updating a row so that a long column is updated or the length
-          of some column changes, <literal>InnoDB</literal> later would
-          fail to reclaim the <literal>BLOB</literal> storage space if
-          the row was deleted. (Bug #18252)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <literal>InnoDB</literal> had a memory leak for duplicate-key
-          errors with tables having 90 columns or more. (Bug #18384)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           Checks for permissions on database operations could be
           performed in a case-insensitive manner (a user with
           permissions on database <literal>MYDATABASE</literal> could by

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-04-11 03:43:51 UTC (rev 1786)
+++ trunk/refman-common/news-5.1.xml	2006-04-11 03:44:31 UTC (rev 1787)
@@ -845,7 +845,7 @@
       <listitem>
         <para>
           The <literal>mysql_close()</literal> C API function leaked
-          handles for share-memory connections on Windows. (Bug #15846)
+          handles for shared-memory connections on Windows. (Bug #15846)
         </para>
       </listitem>
 
@@ -862,17 +862,6 @@
 
       <listitem>
         <para>
-          Checks for permissions on database operations could be
-          performed in a case-insensitive manner (a user with
-          permissions on database <literal>MYDATABASE</literal> could by
-          accident get permissions on database
-          <literal>myDataBase</literal>), if the privilege data were
-          still cached from a previous check. (Bug #17279)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           The server would crash when <literal>SHOW STATUS</literal> was
           called on a server linked with <literal>yaSSL</literal>. (Bug
           #18310)