List:Commits« Previous MessageNext Message »
From:jon Date:October 9 2006 2:48am
Subject:svn commit - mysqldoc@docsrva: r3577 - in trunk: refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-10-09 04:48:04 +0200 (Mon, 09 Oct 2006)
New Revision: 3577

Log:

Updated changelog entries for Bug #20048, Bug #17810, Bug #19835, Bug
#17877 per Support requests from JamesD/Colin.

Fixed wrong bug report # for Bug #14875 changelog entry.

Fixed a few misc. typos.



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


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2006-10-08 07:30:01 UTC (rev 3576)
+++ trunk/refman-4.1/news-4.1.xml	2006-10-09 02:48:04 UTC (rev 3577)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 5; 1126 bytes

@@ -1116,16 +1116,18 @@
 
       <listitem>
         <para>
-          Using <literal>SELECT</literal> on a corrupt table using the
-          dynamic record format could cause a server crash. (Bug #19835)
+          Using <literal>SELECT</literal> on a corrupt
+          <literal>MyISAM</literal> 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)
+          Checking a <literal>MyISAM</literal> table (using
+          <literal>CHECK TABLE</literal>) having a spatial index and
+          only one row would wrongly indicate that the table was
+          corrupted. (Bug #17877)
         </para>
       </listitem>
 


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2006-10-08 07:30:01 UTC (rev 3576)
+++ trunk/refman-5.0/news-5.0.xml	2006-10-09 02:48:04 UTC (rev 3577)
Changed blocks: 5, Lines Added: 17, Lines Deleted: 13; 2821 bytes

@@ -2579,8 +2579,9 @@
 
       <listitem>
         <para>
-          Using <literal>SELECT</literal> on a corrupt table using the
-          dynamic record format could cause a server crash. (Bug #19835)
+          Using <literal>SELECT</literal> on a corrupt
+          <literal>MyISAM</literal> table using the dynamic record
+          format could cause a server crash. (Bug #19835) 
         </para>
       </listitem>
 

@@ -2596,9 +2597,10 @@
 
       <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)
+          Checking a <literal>MyISAM</literal> table (using
+          <literal>CHECK TABLE</literal>) having a spatial index and
+          only one row would wrongly indicate that the table was
+          corrupted. (Bug #17877)
         </para>
       </listitem>
 

@@ -3310,9 +3312,9 @@
 
       <listitem>
         <para>
-          A <quote>table not found</quote> error could occur for
-          statements that called a function defined in another database.
-          (Bug #17199)
+          A <errortext>Table ... doesn't exist</errortext> error could
+          occur for statements that called a function defined in another
+          database. (Bug #17199)
         </para>
       </listitem>
 

@@ -4136,15 +4138,15 @@
           A view with a non-existent account in the
           <literal>DEFINER</literal> clause caused <literal>SHOW CREATE
           VIEW</literal> to fail. Now <literal>SHOW CREATE
-          VIEW</literal> issues a warning instead. (Bug #20048)
+          VIEW</literal> issues a warning instead. (Bug #14875)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          A bug in NTPL threads on Linux could result in a deadlock with
-          <literal>FLUSH TABLES WITH READ LOCK</literal> under some
-          conditions. (Bug #20048)
+          A bug in NPTL (Native POSIX Thread Library) on Linux could
+          result in a deadlock with <literal>FLUSH TABLES WITH READ
+            LOCK</literal> under some conditions. (Bug #20048)
         </para>
       </listitem>
 

@@ -4312,7 +4314,9 @@
       <listitem>
         <para>
           <literal>REPAIR TABLE</literal> did not restore the length for
-          packed keys in tables created under MySQL 4.x. (Bug #17810)
+          packed keys in tables created under MySQL 4.x, which caused
+          them to appear corrupt to <literal>CHECK TABLE</literal> but
+          not to <literal>REPAIR TABLE</literal>. (Bug #17810)
         </para>
       </listitem>
 


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-10-08 07:30:01 UTC (rev 3576)
+++ trunk/refman-5.1/news-5.1.xml	2006-10-09 02:48:04 UTC (rev 3577)
Changed blocks: 2, Lines Added: 13, Lines Deleted: 11; 1996 bytes

@@ -3291,24 +3291,26 @@
 
       <listitem>
         <para>
-          Using <literal>SELECT</literal> on a corrupt table using the
-          dynamic record format could cause a server crash. (Bug #19835)
+          Using <literal>SELECT</literal> on a corrupt
+          <literal>MyISAM</literal> 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)
+          Checking a <literal>MyISAM</literal> table (using
+          <literal>CHECK TABLE</literal>) having a spatial index and
+          only one row would wrongly indicate that the table was
+          corrupted. (Bug #17877)
         </para>
       </listitem>
 
       <listitem>
         <para>
-          A <quote>table not found</quote> error could occur for
-          statements that called a function defined in another database.
-          (Bug #17199)
+          A <errortext>Table ... doesn't exist</errortext> error could
+          occur for statements that called a function defined in another
+          database. (Bug #17199)
         </para>
       </listitem>
 

@@ -5740,9 +5742,9 @@
 
       <listitem>
         <para>
-          A bug in NTPL threads on Linux could result in a deadlock with
-          <literal>FLUSH TABLES WITH READ LOCK</literal> under some
-          conditions. (Bug #20048)
+          A bug in NPTL (Native POSIX Thread Library) on Linux could
+          result in a deadlock with <literal>FLUSH TABLES WITH READ
+            LOCK</literal> under some conditions. (Bug #20048)
         </para>
       </listitem>
 


Thread
svn commit - mysqldoc@docsrva: r3577 - in trunk: refman-4.1 refman-5.0 refman-5.1jon9 Oct