List:Commits« Previous MessageNext Message »
From:mhillyer Date:January 26 2006 3:18am
Subject:svn commit - mysqldoc@docsrva: r1040 - trunk/refman-common
View as plain text  
Author: mhillyer
Date: 2006-01-26 04:18:44 +0100 (Thu, 26 Jan 2006)
New Revision: 1040

Log:
Document bugfixes, format and validate.

3300,10130,14354,15935,15965,16487,15699,16738,16765,16771,15020,15851,15307,9483,16432,16435,16489,16548,9855,14320,15429,15866,3906,14634,13944,15613,3074,14834,15910

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-01-26 00:21:25 UTC (rev 1039)
+++ trunk/refman-common/news-4.0.xml	2006-01-26 03:18:44 UTC (rev 1040)
@@ -173,7 +173,7 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           An <literal>UPDATE</literal> statement which tried to update a

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-01-26 00:21:25 UTC (rev 1039)
+++ trunk/refman-common/news-4.1.xml	2006-01-26 03:18:44 UTC (rev 1040)
@@ -166,28 +166,88 @@
           <literal>NDB Cluster</literal>: More descriptive warnings are
           now issued when inappropriate logging parameters are set in
           <filename>config.ini</filename>. (Formerly, the warning issued
-          was simply <errortext>Could not add logfile
-          destination</errortext>.) (Bug #11331)
+          was simply
+
+          <errortext>Could not add logfile
+          destination</errortext>
+
+          .) (Bug #11331)
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          <literal>libmysqlclient</literal> now uses versioned symbols.
+          (Bug #3074)
+        </para>
+      </listitem>
+
     </itemizedlist>
-    
+
     <para>
       Bugs fixed:
     </para>
-    
+
     <itemizedlist>
+
       <listitem>
         <para>
+          Running out of diskspace in the location specified by the
+          <literal>tmpdir</literal> option resulted in incorrect error
+          message. (Bug #14634)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Test suite <literal>func_math</literal> test returned warnings
+          when server not compiled with InnoDB support. (Bug #15429)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <literal>MBROverlaps</literal> GIS function returned
+          incorrect results. (Bug #14320)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A <literal>CREATE TABLE ... SELECT ...</literal> on an
+          equation involving <literal>DOUBLE</literal> values could
+          result in the table being created with columns too small to
+          hold the equation result. (Bug #9855)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>UPDATE</literal> statement crashed multi-byte
+          character set <literal>FULLTEXT</literal> index. (Bug #16489)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Single table <literal>UPDATE</literal> statements without
+          <literal>ORDER BY</literal> clauses which updated the same
+          indexed column that was being filtered on were optimized with
+          a full index scan instead of a more appropriate index range
+          scan. (Bug #15935)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           A prepared statement created from a <literal>SELECT ...
-            LIKE</literal> query (such as <literal>PREPARE stmt1 FROM
-              'SELECT col_1 FROM tedd_test WHERE col_1 LIKE
-              ?';</literal>)  would begin to produce erratic results
-          after being executed repeatedly numerous (thousands) of times.
-          (Bug #12734)
+          LIKE</literal> query (such as <literal>PREPARE stmt1 FROM
+          'SELECT col_1 FROM tedd_test WHERE col_1 LIKE ?';</literal>)
+          would begin to produce erratic results after being executed
+          repeatedly numerous (thousands) of times. (Bug #12734)
         </para>
       </listitem>
+
     </itemizedlist>
 
   </section>
@@ -220,6 +280,14 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          Internal <literal>sha1_result</literal> function renamed to
+          <literal>mysql_sha1_result</literal> to prevent conflicts with
+          other projects. (Bug #13944)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -230,6 +298,14 @@
 
       <listitem>
         <para>
+          Pipeing the <filename>fill_help_tables.sql</filename> file
+          into <command>mysqld</command> resulted in a syntax error.
+          (Bug #15965)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDBCluster</literal>: Upon the completion of a scan
           where a key request remained outstanding on the primary
           replica and a starting node died, the scan did not terminate.

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-01-26 00:21:25 UTC (rev 1039)
+++ trunk/refman-common/news-5.0.xml	2006-01-26 03:18:44 UTC (rev 1040)
@@ -176,34 +176,45 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
+          <literal>libmysqlclient</literal> now uses versioned symbols.
+          (Bug #3074)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <emphasis role="bold">Incompatible change</emphasis>: The
           <literal>InnoDB</literal> storage engine no longer ignores
           trailing spaces when comparing <literal>BINARY</literal> or
-          <literal>VARBINARY</literal> column values. This means that (for
-          example) the binary values <literal>'a'</literal> and
+          <literal>VARBINARY</literal> column values. This means that
+          (for example) the binary values <literal>'a'</literal> and
           <literal>'a '</literal> are now regarded as
           <emphasis>unequal</emphasis> any time they are compared, as
-          they are in <literal>MyISAM</literal> tables. (Bug #14189)  
+          they are in <literal>MyISAM</literal> tables. (Bug #14189)
         </para>
-        
+
         <para>
           See <xref linkend="binary-varbinary"/> for more information
           about the <literal>BINARY</literal> and
           <literal>VARBINARY</literal> types.
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: More descriptive warnings are
           now issued when inappropriate logging parameters are set in
           <filename>config.ini</filename>. (Formerly, the warning issued
-          was simply <errortext>Could not add logfile
-            destination</errortext>.) (Bug #11331) 
-        </para>        
+          was simply
+
+          <errortext>Could not add logfile
+            destination</errortext>
+
+          .) (Bug #11331)
+        </para>
       </listitem>
 
       <listitem>
@@ -233,6 +244,14 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          The <literal>INFORMATION_SCHEMA</literal> now skips data
+          contained in unlistable/unreadable directories rather than
+          returning an error. (Bug #15851)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -240,43 +259,93 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
+          <literal>GRANT</literal> statements specifying schema names
+          that included underscore characters (i.e.
+          <literal>my_schema</literal>) did not match if the underscore
+          was escaped in the <literal>GRANT</literal> statement (i.e.
+          <literal>GRANT ALL ON `my\_schema` ...</literal>). (Bug
+          #14834)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Running out of diskspace in the location specified by the
+          <literal>tmpdir</literal> option resulted in incorrect error
+          message. (Bug #14634)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Test suite <literal>sp</literal> test left behind tables when
+          the test failed that could cause future tests to fail. (Bug
+          #15866)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>UPDATE</literal> statement crashed multi-byte
+          character set <literal>FULLTEXT</literal> index. (Bug #16489)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A <literal>SELECT</literal> query which contained a
+          <literal>GROUP_CONCAT()</literal> and an <literal>ORDER
+          BY</literal> clause against the
+          <literal>INFORMATION_SCHEMA</literal> resulted in an empty
+          result set. (Bug #15307)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <literal>--replicate-do</literal> and
+          <literal>--replicate-ignore</literal> options were not being
+          enforced on multi-table statements. (Bug #15699, Bug #16487)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           A prepared statement created from a <literal>SELECT ...
-            LIKE</literal> query (such as <literal>PREPARE stmt1 FROM
-              'SELECT col_1 FROM tedd_test WHERE col_1 LIKE
-              ?';</literal>)  would begin to produce erratic results
-          after being executed repeatedly numerous (thousands) of times.
-          (Bug #12734)
+          LIKE</literal> query (such as <literal>PREPARE stmt1 FROM
+          'SELECT col_1 FROM tedd_test WHERE col_1 LIKE ?';</literal>)
+          would begin to produce erratic results after being executed
+          repeatedly numerous (thousands) of times. (Bug #12734)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           The server would crash when the size of an
           <literal>ARCHIVE</literal> table grew beyond 2GB. (Bug #15787)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Created a user function with an empty string (that is,
           <literal>CREATE FUNCTION ''()</literal>), was accepted by the
           server. Following this, calling <literal>SHOW FUNCTION
-            STATUS</literal> would cause the server to crash. (Bug
-          #15658)
+          STATUS</literal> would cause the server to crash. (Bug #15658)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           In some cases the query optimizer did not properly perform
           multiple joins where inner joins followed left joins,
-          resulting in corrupted result sets. (Bug #15633) 
+          resulting in corrupted result sets. (Bug #15633)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           The absence of a table in the left part of a left or right
@@ -284,14 +353,14 @@
           in a server crash. (Bug #15538)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal>: A bitfield whose offset and
           length totaled 32 would crash the cluster. (Bug #16125)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal>: Upon the completion of a scan
@@ -301,7 +370,7 @@
           (Bug #15908)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal>: The
@@ -310,34 +379,36 @@
           (Bug #15619)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal>: When running more than one
           management process in a cluster:
         </para>
-        
+
         <itemizedlist>
+
           <listitem>
             <para>
               <command>ndb_mgm -c
-                <replaceable>host</replaceable>:<replaceable>port</replaceable>
-                -e "<replaceable>node_id</replaceable> stop"</command>
+              <replaceable>host</replaceable>:<replaceable>port</replaceable>
+              -e "<replaceable>node_id</replaceable> stop"</command>
               would stop a management process running only on the same
               system on which the command was issued.
             </para>
           </listitem>
-          
+
           <listitem>
             <para>
               <command>ndb_mgm -e "shutdown"</command> failed to shut
-              down any management processes at all.              
+              down any management processes at all.
             </para>
-          </listitem>          
+          </listitem>
+
         </itemizedlist>
-          
+
         <para>
-          (Bug #12045, Bug #12124) 
+          (Bug #12045, Bug #12124)
         </para>
       </listitem>
 
@@ -11896,6 +11967,16 @@
 
       <listitem>
         <para>
+          The output of the <literal>SHOW BINLOG EVENTS</literal>
+          statement has been modified. The
+          <literal>Orig_log_pos</literal> column has been renamed to
+          <literal>End_log_pos</literal> and now represents the offset
+          of the last byte of the event, plus one.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <emphasis role="bold">Important note:</emphasis> If you
           upgrade to MySQL 4.1.1 or higher, it is difficult to downgrade
           back to 4.0 or 4.1.0! That is because, for earlier versions,

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-01-26 00:21:25 UTC (rev 1039)
+++ trunk/refman-common/news-5.1.xml	2006-01-26 03:18:44 UTC (rev 1040)
@@ -153,13 +153,6 @@
 
       <listitem>
         <para>
-          Subselect could return wrong results when records cache and
-          grouping was involved. (Bug #15347)
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           The <literal>ARCHIVE</literal> storage engine supports the
           <literal>AUTO_INCREMENT</literal> column attribute and the
           <literal>AUTO_INCREMENT</literal> table option.
@@ -174,15 +167,85 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
+          Error message for specifying value for which no partition
+          exists returned wrong values on certain platforms. (Bug
+          #15910)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Certain Japanese table names were not properly saved during a
+          <literal>CREATE TABLE</literal> statement. (Bug #3906)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>CREATE EVENT</literal> statement with <literal>ON
+          COMPLETION</literal> clause but no <literal>ON
+          SCHEDULE</literal> clause resulted in syntax error. (Bug
+          #16548)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Interval type was ignored in a <literal>CREATE EVENT</literal>
+          statement. (Bug #16435)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Specifying a excessively large interval in a <literal>CREATE
+          EVENT</literal> statement resulted in an inaccurate
+          <literal>INTERVAL must be positive</literal> error message.
+          (Bug #16432)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          NDB Cluster leaked disk space when performing INSERTS/DELETES
+          in a loop. (Bug #16771)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          NDB Cluster returned wrong error when tablespace on disk was
+          full. (Bug #16738)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The <literal>DATA DIRECTORY</literal> and <literal>INDEX
+          DIRECTORY</literal> clauses of a <literal>CREATE
+          TABLE</literal> statement involving partitions did not work.
+          (Bug #14354)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Subselect could return wrong results when records cache and
+          grouping was involved. (Bug #15347)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           In some cases the query optimizer did not properly perform
           multiple joins where inner joins followed left joins,
-          resulting in corrupted result sets. (Bug #15633) 
+          resulting in corrupted result sets. (Bug #15633)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           The absence of a table in the left part of a left or right
@@ -190,7 +253,7 @@
           in a server crash. (Bug #15538)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Trying to import too many
@@ -200,28 +263,28 @@
           #16455)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (Disk Data): Tablespaces
           created using parameters with relatively low values (&lt; 10
           MB) produced filesizes much smaller than expected. (Bug
-          #16742)          
+          #16742)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: <literal>CREATE
-            TABLESPACE</literal> statements were incorrectly parsed on
+          TABLESPACE</literal> statements were incorrectly parsed on
           64-bit platforms. (<literal>INITIAL SIZE
-            <replaceable>size</replaceable></literal> worked, but
+          <replaceable>size</replaceable></literal> worked, but
           <literal>INITIAL SIZE =
           <replaceable>size</replaceable></literal> failed.) (Bug
           #13556)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Trying to add more than one partition in a single
@@ -229,7 +292,7 @@
           caused the server to crash. (Bug #16534)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Creating a partitioned table using a storage engine other than
@@ -237,7 +300,7 @@
           (Bug #15966)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           An <literal>ALTER TABLE ... PARTITION BY ...</literal>
@@ -336,7 +399,10 @@
       <listitem>
         <para>
           <literal>ALTER TABLE ... ADD PARTITION</literal> could crash
-          the server or cause an <errortext>Out of memory</errortext>
+          the server or cause an
+
+          <errortext>Out of memory</errortext>
+
           error in some circumstances. (Bug #13447)
         </para>
       </listitem>
@@ -531,15 +597,15 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>InnoDB</literal>: An <literal>UPDATE</literal>
           statement with no index column in the <literal>WHERE</literal>
-          condition locked all the rows in the table. (Bug #3300) 
+          condition locked all the rows in the table. (Bug #3300)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>INSERT DELAYED</literal> caused
@@ -618,10 +684,14 @@
           <literal>LIST</literal> a value less than any specified in one
           of the table's partition definitions resulted in a server
           crash. In such cases, <command>mysqld</command> now returns
+
           <errortext>ERROR 1500 (HY000): Table has no partition for
-          value <replaceable>v</replaceable></errortext>, where
-          <replaceable>v</replaceable> is the out-of-range value. (Bug
-          #15819)
+          value <replaceable>v</replaceable>
+
+          </errortext>
+
+          , where <replaceable>v</replaceable> is the out-of-range
+          value. (Bug #15819)
         </para>
       </listitem>
 
@@ -767,8 +837,11 @@
 
         <para>
           Previously, attempting to do so would produce the error
+
           <errortext>All partitions must have unique names in the
-          table</errortext>. (Bug #15521)
+          table</errortext>
+
+          . (Bug #15521)
         </para>
       </listitem>
 

Thread
svn commit - mysqldoc@docsrva: r1040 - trunk/refman-commonmhillyer26 Jan