List:Commits« Previous MessageNext Message »
From:paul Date:January 24 2006 4:51am
Subject:svn commit - mysqldoc@docsrva: r1013 - in trunk: . refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-24 05:51:18 +0100 (Tue, 24 Jan 2006)
New Revision: 1013

Log:
 r6621@frost:  paul | 2006-01-23 22:50:14 -0600
 have_partition_engine -> have_partitioning


Modified:
   trunk/
   trunk/refman-5.1/database-administration.xml
   trunk/refman-5.1/partitioning.xml
   trunk/refman-5.1/sql-syntax.xml
   trunk/refman-common/news-5.1.xml


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

Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2006-01-24 04:50:25 UTC (rev 1012)
+++ trunk/refman-5.1/database-administration.xml	2006-01-24 04:51:18 UTC (rev 1013)
@@ -2182,7 +2182,7 @@
 | have_isam                       | NO                                        |
 | have_ndbcluster                 | DISABLED                                  |
 | have_openssl                    | NO                                        |
-| have_partition_engine           | YES                                       |
+| have_partitioning               | YES                                       |
 | have_query_cache                | YES                                       |
 | have_raid                       | NO                                        |
 | have_rtree_keys                 | YES                                       |
@@ -3638,12 +3638,12 @@
 
           <listitem>
             <para>
-              <literal>have_partition_engine</literal>
+              <literal>have_partitioning</literal>
             </para>
 
             <para>
               <literal>YES</literal> if <command>mysqld</command>
-              supports partitioning. Added in MySQL 5.1.1.
+              supports partitioning. Added in MySQL 5.1.1 as <literal>have_partition_engine</literal> and renamed to <literal>have_partioning</literal> in 5.1.6.
             </para>
           </listitem>
 

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-01-24 04:50:25 UTC (rev 1012)
+++ trunk/refman-5.1/partitioning.xml	2006-01-24 04:51:18 UTC (rev 1013)
@@ -237,16 +237,16 @@
 <programlisting>
 mysql&gt; <userinput>SHOW VARIABLES LIKE '%partition%';</userinput>
 
-+-----------------------+-------+
-| Variable_name         | Value |
-+-----------------------+-------+
-| have_partition_engine | YES   |
-+-----------------------+-------+
++-------------------+-------+
+| Variable_name     | Value |
++-------------------+-------+
+| have_partitioning | YES   |
++-------------------+-------+
 1 row in set (0.00 sec)
 </programlisting>
 
     <para>
-      If you do not see the <literal>have_partition_engine</literal>
+      If you do not see the <literal>have_partitioning</literal>
       variable with the value <literal>YES</literal> listed as shown
       above in the output of an appropriate <literal>SHOW
       VARIABLES</literal>, then your version of MySQL does not support

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-01-24 04:50:25 UTC (rev 1012)
+++ trunk/refman-5.1/sql-syntax.xml	2006-01-24 04:51:18 UTC (rev 1013)
@@ -17673,7 +17673,7 @@
 | have_isam             | NO       |
 | have_ndbcluster       | DISABLED |
 | have_openssl          | NO       |
-| have_partition_engine | YES      |
+| have_partitioning     | YES      |
 | have_query_cache      | YES      |
 | have_raid             | NO       |
 | have_rtree_keys       | YES      |

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-01-24 04:50:25 UTC (rev 1012)
+++ trunk/refman-common/news-5.1.xml	2006-01-24 04:51:18 UTC (rev 1013)
@@ -21,15 +21,15 @@
   </para>
 
   <itemizedlist>
-    
+
     <listitem>
       <para>
         MySQL 5.1 enables table partitioning with a selection of
         partitioning algorithms and options available, independently of
         the storage engine used by the table. Syntactically, this
         implements a number of new extensions to the <literal>CREATE
-          TABLE</literal>, <literal>ALTER TABLE</literal>, and
-        <literal>EXPLAIN ... SELECT</literal> statements. See 
+        TABLE</literal>, <literal>ALTER TABLE</literal>, and
+        <literal>EXPLAIN ... SELECT</literal> statements. See
         <xref linkend="partitioning"/>.
       </para>
     </listitem>
@@ -75,18 +75,18 @@
           read partitioned tables created in previous MySQL versions. A
           suggested workaround is (1) to create a non-partitioned table
           with the same table schema using a standard <literal>CREATE
-            TABLE</literal> statement (that is, with no partitioning
+          TABLE</literal> statement (that is, with no partitioning
           clauses) and then (2) to issue a<literal>SELECT INTO</literal>
           to copy the data into the non-partitioned table before the
           upgrade; following the upgrade, you can partition the new
           table using <literal>ALTER TABLE ... PARTITION BY
-            ...</literal>. Alternatively, you can dump the table using
+          ...</literal>. Alternatively, you can dump the table using
           <command>mysqldump</command> prior to upgrading and reload it
           afterwards with <literal>LOAD DATA</literal>. In either case,
           you should drop the pre-5.1.6 partitioned tables before
-          upgrading to 5.1.6 or later. (Bug #13437)       
+          upgrading to 5.1.6 or later. (Bug #13437)
         </para>
-        
+
         <para>
           <emphasis role="bold">Important</emphasis>: If any partitioned
           tables that were created prior to MySQL 5.1.6 are present
@@ -113,15 +113,17 @@
           #14194)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Partition support is not an <quote>engine</quote>, but it was
           included in the output of <literal>SHOW ENGINES</literal>. Now
-          it does not. (Bug #14355)
+          it does not. (Bug #14355) The
+          <literal>have_partition_engine</literal> was renamed to
+          <literal>have_partitioning</literal>. (Bug #16718)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>ANALYZE TABLE</literal> is now supported for
@@ -172,7 +174,7 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal> (Disk Data): The error message
@@ -180,23 +182,23 @@
           provide any reasons for the failure. (Bug #16267)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal> (Disk Data): <literal>DROP
-            LOGFILE GROUP</literal> corrupted the cluster file system
-          and caused <command>ndbd</command> to fail when running more
-          than one node on the same system. (Bug #16193)
+          LOGFILE GROUP</literal> corrupted the cluster file system and
+          caused <command>ndbd</command> to fail when running more than
+          one node on the same system. (Bug #16193)
         </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
@@ -206,7 +208,7 @@
           (Bug #15908)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDBCluster</literal>: The
@@ -215,7 +217,7 @@
           (Bug #15619)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Using <command>mysqldump</command> to obtain a dump of a
@@ -233,7 +235,7 @@
           #14327)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Inserting a negative value into an integer column used as the
@@ -242,16 +244,16 @@
           #15968)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           With a table partitioned by <literal>LIST</literal>, inserting
           a value which was smaller than any value shown in the
           partitioning value-lists could cause the server to crash. (Bug
-          #14365) 
+          #14365)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>ALTER TABLE ... DROP PARTITION</literal> would
@@ -260,7 +262,7 @@
           #13644)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>ALTER TABLE ... ADD PARTITION</literal> could crash
@@ -268,16 +270,16 @@
           error in some circumstances. (Bug #13447)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           The server would allow foreign keys to be declared in the
           definition of a partitioned table despite the fact that
-          partitioned tables do not support foreign keys (see 
-          <xref linkend="partitioning-limitations"/>). (Bug #13446) 
+          partitioned tables do not support foreign keys (see
+          <xref linkend="partitioning-limitations"/>). (Bug #13446)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           A <literal>SELECT</literal> from a key-partitioned table with
@@ -285,7 +287,7 @@
           #13445)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Issuing a <literal>TRUNCATE</literal> statement twice in
@@ -293,14 +295,14 @@
           server to crash. (Bug #13442)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Using a <literal>REPLACE</literal> statement on a partitioned
           table caused the server to crash. (Bug #13440)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Using an identifier rather than a literal integer value in the
@@ -309,7 +311,7 @@
           tables. (Bug #13439)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           Using <literal>ENGINE=...</literal> within a
@@ -317,7 +319,7 @@
           crash. (Bug #13438)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>CREATE TABLE ... LIKE</literal> did not work if the
@@ -325,7 +327,7 @@
           (Bug #13435)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>SHOW CREATE TABLE</literal> did not display the
@@ -386,8 +388,8 @@
 
       <listitem>
         <para>
-          Added the <literal>INFORMATION_SCHEMA PLUGINS</literal> table and
-the <literal>SHOW PLUGIN</literal> statement.
+          Added the <literal>INFORMATION_SCHEMA PLUGINS</literal> table
+          and the <literal>SHOW PLUGIN</literal> statement.
         </para>
       </listitem>
 

Thread
svn commit - mysqldoc@docsrva: r1013 - in trunk: . refman-5.1 refman-commonpaul24 Jan