List:Commits« Previous MessageNext Message »
From:paul Date:December 9 2005 12:38am
Subject:svn commit - mysqldoc@docsrva: r529 - in trunk: . refman-5.0 refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2005-12-09 01:38:20 +0100 (Fri, 09 Dec 2005)
New Revision: 529

Log:
 r4632@frost:  paul | 2005-12-08 18:37:59 -0600
 Document bugfixes:
 11555
 14233
 15441
 15510
 15028
 15512
 13293
 13421
 14155
 14780
 14221
 14902


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


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4626
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1505
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4632
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1505

Modified: trunk/refman-5.0/stored-procedures.xml
===================================================================
--- trunk/refman-5.0/stored-procedures.xml	2005-12-08 20:44:14 UTC (rev 528)
+++ trunk/refman-5.0/stored-procedures.xml	2005-12-09 00:38:20 UTC (rev 529)
@@ -111,6 +111,13 @@
     </para>
 
     <para>
+      The server manipulates the <literal>mysql.proc</literal> table in
+      response to statements that create, alter, or drop stored
+      routines. It is not supported that the server will notice manual
+      manipulation of this table.
+    </para>
+
+    <para>
       Beginning with MySQL 5.0.3, the grant system has been modified to
       take stored routines into account as follows:
     </para>

Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml	2005-12-08 20:44:14 UTC (rev 528)
+++ trunk/refman-5.1/stored-procedures.xml	2005-12-09 00:38:20 UTC (rev 529)
@@ -111,6 +111,13 @@
     </para>
 
     <para>
+      The server manipulates the <literal>mysql.proc</literal> table in
+      response to statements that create, alter, or drop stored
+      routines. It is not supported that the server will notice manual
+      manipulation of this table.
+    </para>
+
+    <para>
       In MySQL &current-series;, the grant system takes stored routines
       into account as follows:
     </para>

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2005-12-08 20:44:14 UTC (rev 528)
+++ trunk/refman-common/news-4.1.xml	2005-12-09 00:38:20 UTC (rev 529)
@@ -159,10 +159,21 @@
       Functionality added or changed:
     </para>
 
-    <remark>
-      ADD AN ITEMIZED LIST WHEN WE HAVE SOME ITEMS THAT GO HERE
-    </remark>
+    <itemizedlist>
 
+      <listitem>
+        <para>
+          In the <literal>latin5_turkish_ci</literal> collation, the
+          order of the characters <literal>A WITH CIRCUMFLEX</literal>,
+          <literal>I WITH CIRCUMLEX</literal>, and <literal>U WITH
+          CIRCUMFLEX</literal> was changed. If you have used these
+          characters in any indexed columns, you should rebuild those
+          indexes. (Bug#13421)
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
     <para>
       Bugs fixed:
     </para>
@@ -171,6 +182,15 @@
 
       <listitem>
         <para>
+          Multiple-table update operations were counting updates and not
+          updated rows. As a result, if a row had several updates it was
+          counted several times for the <quote>rows matched</quote>
+          value but updated only once. (Bug #15028)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>SELECT</literal> queries that began with an opening
           parenthesis were not being placed in the query cache. (Bug
           #14652)
@@ -276,6 +296,18 @@
 
       <listitem>
         <para>
+          Portability fixes to support OpenSSL 0.9.8a. (Bug #14221)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Closed a memory leak in the SSL code. (Bug #14780)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Perform character set conversion of constant values whenever
           possible without data loss. (Bug #10446)
         </para>

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2005-12-08 20:44:14 UTC (rev 528)
+++ trunk/refman-common/news-5.0.xml	2005-12-09 00:38:20 UTC (rev 529)
@@ -204,10 +204,18 @@
       Bugs fixed:
     </para>
 
-    <remark>
-      ADD AN ITEMIZED LIST WHEN WE HAVE SOME ITEMS THAT GO HERE
-    </remark>
+    <itemizedlist>
 
+      <listitem>
+        <para>
+          Resolution of the argument to the <literal>VALUES()</literal>
+          function to a variable inside a stored routine caused a server
+          crash. The argument must be a table column. (Bug #15441)
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
   </section>
 
   <section id="news-5-0-17">
@@ -252,6 +260,17 @@
         </para>
       </listitem>
 
+      <listitem>
+        <para>
+          In the <literal>latin5_turkish_ci</literal> collation, the
+          order of the characters <literal>A WITH CIRCUMFLEX</literal>,
+          <literal>I WITH CIRCUMLEX</literal>, and <literal>U WITH
+          CIRCUMFLEX</literal> was changed. If you have used these
+          characters in any indexed columns, you should rebuild those
+          indexes. (Bug#13421)
+        </para>
+      </listitem>
+
     </itemizedlist>
 
     <para>
@@ -262,6 +281,67 @@
 
       <listitem>
         <para>
+          <literal>ANALYZE TABLE</literal> did not properly update table
+          statistics for a <literal>MyISAM</literal> table with a
+          <literal>FULLTEXT</literal> index containing stopwords, so a
+          subsequent <literal>ANALYZE TABLE</literal> would not
+          recognize the table as having already been analyzed. (Bug
+          #14902)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The maximum value of <literal>MAX_ROWS</literal> was handled
+          incorrectly on 64-bit systems. (Bug #14155)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: A forced cluster shutdown
+          occurred when the management daemon was restarted with a
+          changed <filename>config.ini</filename> file that added an
+          API/SQL node. (Bug #15512)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Multiple-table update operations were counting updates and not
+          updated rows. As a result, if a row had several updates it was
+          counted several times for the <quote>rows matched</quote>
+          value but updated only once. (Bug #15028)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          A statement that produced a warning, when fetched via
+          <literal>mysql_stmt_fetch()</literal>, did not produce a
+          warning count according to
+          <literal>mysql_warning_count()</literal>. (Bug #15510)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Manual manipulation of the <literal>mysql.proc</literal> table
+          could cause a server crash. This should not happen, but it is
+          also not supported that the server will notice such changes.
+          (Bug #14233)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Revised table locking locking to allow proper assessment of
+          view security. (Bug #11555)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Within a stored procedure, inserting with <literal>INSERT
           &hellip; SELECT</literal> into a table with an
           <literal>AUTO_INCREMENT</literal> column did not generate the
@@ -849,6 +929,16 @@
 
       <listitem>
         <para>
+          <literal>InnoDB</literal>: When dropping and adding a
+          <literal>PRIMARY KEY</literal>, if a loose index scan using
+          only the second part of multiple-part index was chosen,
+          incorrect keys were created and an endless loop resulted. (Bug
+          #13293)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: Repeated transactions using
           unique index lookups could cause a memory leak leading to
           error 288, <literal>Out of index operations in transaction

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2005-12-08 20:44:14 UTC (rev 528)
+++ trunk/refman-common/news-5.1.xml	2005-12-09 00:38:20 UTC (rev 529)
@@ -84,6 +84,33 @@
 
       <listitem>
         <para>
+          <literal>ANALYZE TABLE</literal> did not properly update table
+          statistics for a <literal>MyISAM</literal> table with a
+          <literal>FULLTEXT</literal> index containing stopwords, so a
+          subsequent <literal>ANALYZE TABLE</literal> would not
+          recognize the table as having already been analyzed. (Bug
+          #14902)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          The maximum value of <literal>MAX_ROWS</literal> was handled
+          incorrectly on 64-bit systems. (Bug #14155)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Multiple-table update operations were counting updates and not
+          updated rows. As a result, if a row had several updates it was
+          counted several times for the <quote>rows matched</quote>
+          value but updated only once. (Bug #15028)
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <literal>SELECT</literal> queries that began with an opening
           parenthesis were not being placed in the query cache. (Bug
           #14652)
@@ -202,118 +229,119 @@
     <para>
       Functionality added or changed:
     </para>
-    
+
     <para>
       This is the first public alpha release of the current MySQL 5.1
-      development branch, providing an insight to upcoming features. While
-      some of these are still under heavy development, this release includes
-      the following new features and changes (in comparison to the current
-      MySQL 5.0 production release):
+      development branch, providing an insight to upcoming features.
+      While some of these are still under heavy development, this
+      release includes the following new features and changes (in
+      comparison to the current MySQL 5.0 production release):
     </para>
-    
+
     <itemizedlist>
-      
+
       <listitem>
         <para>
-          <emphasis role="bold">Partitioning</emphasis>:
-          allows distributing portions of individual tables
-          across a filesystem, according to rules which can be set when the
-          table is created. In effect, different portions of a table are stored
-          as separate tables in different locations, but from the user
-          point of view, the partitioned table is still a single table. See
-          <xref linkend="partitioning"/> for further
+          <emphasis role="bold">Partitioning</emphasis>: allows
+          distributing portions of individual tables across a
+          filesystem, according to rules which can be set when the table
+          is created. In effect, different portions of a table are
+          stored as separate tables in different locations, but from the
+          user point of view, the partitioned table is still a single
+          table. See <xref linkend="partitioning"/> for further
           information on this functionality. (Author: Mikael Ronström)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <emphasis role="bold">Plugin API</emphasis>:
-          MySQL 5.1 will add support for a very flexible plugin API that will
-          allow the loading and unloading of various components at runtime,
-          without restarting the server. While the work on this are not finished
-          yet, <emphasis>pluggable full-text parsers</emphasis> 
-          are a first step in this direction.
-          This allows users to implement their own input filter on the indexed
-          text, enabling full-text search capability on arbitrary data like PDF
-          files or other document formats. A pre-parser full-text plugin
-          performs the actual parsing and extraction of the text and hands it
-          over to the builtin MySQL full-text search.
-          (Author: Sergey Vojtovich)
+          <emphasis role="bold">Plugin API</emphasis>: MySQL 5.1 will
+          add support for a very flexible plugin API that will allow the
+          loading and unloading of various components at runtime,
+          without restarting the server. While the work on this are not
+          finished yet, <emphasis>pluggable full-text parsers</emphasis>
+          are a first step in this direction. This allows users to
+          implement their own input filter on the indexed text, enabling
+          full-text search capability on arbitrary data like PDF files
+          or other document formats. A pre-parser full-text plugin
+          performs the actual parsing and extraction of the text and
+          hands it over to the builtin MySQL full-text search. (Author:
+          Sergey Vojtovich)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <emphasis role="bold">The Instance Manager (IM)</emphasis> 
-          now has some additional functionality:
-          
+          <emphasis role="bold">The Instance Manager (IM)</emphasis> now
+          has some additional functionality:
+
           <itemizedlist>
-            
+
             <listitem>
               <para>
-                <literal>SHOW <replaceable>instance_name</replaceable> LOG FILES</literal>
-                provides a listing of all log files used by the instance. (Author: Petr Chardin)
-               </para>
+                <literal>SHOW <replaceable>instance_name</replaceable>
+                LOG FILES</literal> provides a listing of all log files
+                used by the instance. (Author: Petr Chardin)
+              </para>
             </listitem>
-            
+
             <listitem>
               <para>
-                <literal>SHOW <replaceable>instance_name</replaceable> 
-                LOG {ERROR | SLOW | GENERAL} <replaceable>size</replaceable></literal>
-                retrieves a part of the specified log file. (Author: Petr Chardin)
+                <literal>SHOW <replaceable>instance_name</replaceable>
+                LOG {ERROR | SLOW | GENERAL}
+                <replaceable>size</replaceable></literal> retrieves a
+                part of the specified log file. (Author: Petr Chardin)
               </para>
             </listitem>
-            
+
             <listitem>
               <para>
                 <literal>SET <replaceable>instance_name</replaceable>.
                 <replaceable>option_name</replaceable>=<replaceable>option_value</replaceable></literal>
-                sets an option to
-                the specified value and writes it to the config file
-                See <xref linkend="instance-manager"/> for
-                more details on these new commands. (Author: Petr Chardin)
+                sets an option to the specified value and writes it to
+                the config file See <xref linkend="instance-manager"/>
+                for more details on these new commands. (Author: Petr
+                Chardin)
               </para>
             </listitem>
-            
+
           </itemizedlist>
-          
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Two new aggregate functions, <function>STDDEV_POP</function> 
-          and <function>STDDEV_SAMP</function>, for computing
-          the population and sample standard deviation of expressions.
-          See <xref linkend="group-by-functions"/>
-          for more info. (Author: Sergey Vojtovich)
+          Two new aggregate functions, <function>STDDEV_POP</function>
+          and <function>STDDEV_SAMP</function>, for computing the
+          population and sample standard deviation of expressions. See
+          <xref linkend="group-by-functions"/> for more info. (Author:
+          Sergey Vojtovich)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          The performance of boolean full-text searches (using the <quote>+</quote>
-          Operator) has been improved. See
-          <xref linkend="fulltext-search"/>
-          for more details about full-text searching.
-          (Author: Sergey Vojtovich)
+          The performance of boolean full-text searches (using the
+          <quote>+</quote> Operator) has been improved. See
+          <xref linkend="fulltext-search"/> for more details about
+          full-text searching. (Author: Sergey Vojtovich)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
-          <literal>VARCHAR</literal> fields used in MySQL Cluster 
-          tables are now variable-sized;
-          that is, they now only allocate as much space as required to store
-          the data. Previously, a <literal>VARCHAR(<replaceable>n</replaceable>)</literal> 
-          column allocated n+2 bytes (aligned
-          to 4 bytes), regardless if the actual inserted value required that
-          much space. (In other words, a <literal>VARCHAR</literal> column always required the
-          same, fixed, amount of storage as a <literal>CHAR</literal> column of the same size.)
+          <literal>VARCHAR</literal> fields used in MySQL Cluster tables
+          are now variable-sized; that is, they now only allocate as
+          much space as required to store the data. Previously, a
+          <literal>VARCHAR(<replaceable>n</replaceable>)</literal>
+          column allocated n+2 bytes (aligned to 4 bytes), regardless if
+          the actual inserted value required that much space. (In other
+          words, a <literal>VARCHAR</literal> column always required the
+          same, fixed, amount of storage as a <literal>CHAR</literal>
+          column of the same size.)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Renamed the <literal>table_cache</literal> system variable to

Thread
svn commit - mysqldoc@docsrva: r529 - in trunk: . refman-5.0 refman-5.1 refman-commonpaul9 Dec