From: jon
Date: December 23 2006 6:52am
Subject: svn commit - mysqldoc@docsrva: r4337 - branches/telcos/query-browser branches/telcos/refman-5.1 trunk/refman-5.1
List-Archive: http://lists.mysql.com/commits/17351
Message-Id: <200612230652.kBN6qhsf025230@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-12-23 07:52:41 +0100 (Sat, 23 Dec 2006)
New Revision: 4337

Log:

Merging recent changes to telcos branch; updated the current release
entity's definition.



Modified:
   branches/telcos/query-browser/using.xml
   branches/telcos/refman-5.1/faqs.xml
   branches/telcos/refman-5.1/partitioning.xml
   branches/telcos/refman-5.1/sql-syntax.xml
   branches/telcos/refman-5.1/versions.ent
   trunk/refman-5.1/partitioning.xml


Modified: branches/telcos/query-browser/using.xml
===================================================================
--- branches/telcos/query-browser/using.xml	2006-12-23 06:37:20 UTC (rev 4336)
+++ branches/telcos/query-browser/using.xml	2006-12-23 06:52:41 UTC (rev 4337)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 641 bytes

@@ -251,6 +251,12 @@
       executed, click the <guibutton>Create View</guibutton> button,
       provide a name for the view, and the view is created.
     </para>
+    
+    <note>
+      <para>
+        Creating views is not yet supported on all Operating systems.
+      </para>
+    </note>
 
     <para>
       You can also create a view by right-clicking on the database you


Modified: branches/telcos/refman-5.1/faqs.xml
===================================================================
--- branches/telcos/refman-5.1/faqs.xml	2006-12-23 06:37:20 UTC (rev 4336)
+++ branches/telcos/refman-5.1/faqs.xml	2006-12-23 06:52:41 UTC (rev 4337)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 0; 781 bytes

@@ -4351,6 +4351,22 @@
 
   </section>
 
+<!--
+  <section id="faqs-partitioning">
+    <title>MySQL &current-series; FAQ &mdash; User-Defined Partitioning</title>
+
+    <indexterm>
+      <primary>Partitioning</primary>
+      <secondary>FAQ</secondary>
+    </indexterm>
+
+    <indexterm>
+      <primary>Partitioning</primary>
+      <secondary>frequently asked questions</secondary>
+    </indexterm>
+  </section>
+-->  
+  
   <section id="faqs-cjk">
 
     <title>MySQL &current-series; FAQ &mdash; MySQL Chinese, Japanese, and Korean


Modified: branches/telcos/refman-5.1/partitioning.xml
===================================================================
--- branches/telcos/refman-5.1/partitioning.xml	2006-12-23 06:37:20 UTC (rev 4336)
+++ branches/telcos/refman-5.1/partitioning.xml	2006-12-23 06:52:41 UTC (rev 4337)
Changed blocks: 4, Lines Added: 28, Lines Deleted: 4; 2710 bytes

@@ -4705,17 +4705,33 @@
       </listitem>
 
       <listitem>
+        <indexterm>
+          <primary>Partitioning</primary>
+          <secondary>maximum number of partitions</secondary>
+        </indexterm>
+        
         <para>
+          The maximum number of partitions possible for a given table is
+          1024. This includes subpartitions.
+        </para>
+        
+        <para>
           If, when creating tables with a very large number of
-          partitions, you encounter an error message such as
-          <errortext>Got error 24 from storage engine</errortext>, you
-          may need to increase the value of the
+          partitions (but which is less than the maxmimum stated
+          previously), you encounter an error message such as
+          <errortext>Got error 24 from storage engine</errortext>, this
+          means that you may need to increase the value of the
           <literal>open_files_limit</literal> system variable. See
           <xref linkend="not-enough-file-handles"/>.
         </para>
       </listitem>
 
       <listitem>
+        <indexterm>
+          <primary>partitioning</primary>
+          <secondary>and foreign keys</secondary>
+        </indexterm>
+        
         <para>
           Partitioned tables do not support foreign keys. This includes
           partitioned tables employing the <literal>InnoDB</literal>

@@ -4724,6 +4740,10 @@
       </listitem>
 
       <listitem>
+        <indexterm>
+          <primary>partitioning</primary>
+          <secondary>and FULLTEXT indexes</secondary>
+        </indexterm>
         <para>
           Partitioned tables do not support <literal>FULLTEXT</literal>
           indexes. This includes partitioned tables employing the

@@ -4739,6 +4759,10 @@
       </listitem>
 
       <listitem>
+        <indexterm>
+          <primary>partitioning</primary>
+          <secondary>and temporary tables</secondary>
+        </indexterm>
         <para>
           As of MySQL 5.1.8, temporary tables cannot be partitioned.
           (Bug #17497)

@@ -4806,7 +4830,7 @@
         </para>
 
         <para>
-          The one exception to this restriction occurs when partitioning
+          The lone exception to this restriction occurs when partitioning
           by [<literal>LINEAR</literal>] <literal>KEY</literal> &mdash;
           where it is possible to use columns of other types types as
           partitioning keys &mdash; because MySQL's internal key-hashing


Modified: branches/telcos/refman-5.1/sql-syntax.xml
===================================================================
--- branches/telcos/refman-5.1/sql-syntax.xml	2006-12-23 06:37:20 UTC (rev 4336)
+++ branches/telcos/refman-5.1/sql-syntax.xml	2006-12-23 06:52:41 UTC (rev 4337)
Changed blocks: 3, Lines Added: 18, Lines Deleted: 15; 2868 bytes

@@ -3232,20 +3232,9 @@
       <para>
         <replaceable>partition_options</replaceable> can be used to
         control partitioning of the table created with <literal>CREATE
-        TABLE</literal>, and if used, must contain at a minimum a
-        <literal>PARTITION BY</literal> clause. This clause contains the
-        function that is used to determine the partition; the function
-        returns an integer value ranging from 1 to
-        <replaceable>num</replaceable>, where
-        <replaceable>num</replaceable> is the number of partitions. The
-        choices that are available for this function in MySQL
-        &current-series; are shown in the following list.
-      </para>
-
-      <para>
-        <emphasis role="bold">Important</emphasis>: Not all options
-        shown in the syntax for
-        <replaceable>partition_options</replaceable> at the beginning of
+        TABLE</literal>. <emphasis role="bold">Important</emphasis>:
+        Not all options shown in the syntax for
+        <replaceable>partition_options</replaceable> at the beginning of  
         this section are available for all partitioning types. Please
         see the listings for the following individual types for
         information specific to each type, and see

@@ -3254,6 +3243,20 @@
         well as additional examples of table creation and other
         statements relating to MySQL partitioning.
       </para>
+      
+      <para>
+        If used, <replaceable>partition_options</replaceable> must
+        contain at a minimum a <literal>PARTITION BY</literal> clause.
+        This clause contains the function that is used to determine the
+        partition; the function returns an integer value ranging from 1
+        to <replaceable>num</replaceable>, where
+        <replaceable>num</replaceable> is the number of partitions. (The
+        maxmimum number of user-defined partitions which a table may
+        contain is 1024; the number of subpartitions &mdash; discussed
+        later in this section &mdash; is included in this maxmimum.) The
+        choices that are available for this function in MySQL
+        &current-series; are shown in the following list:
+      </para>
 
       <itemizedlist>
 

@@ -3541,7 +3544,7 @@
 
         <listitem>
           <para>
-            MySQL 5.1.12 introduces rigourous checking of the value used
+            MySQL 5.1.12 introduces rigorous checking of the value used
             in a <literal>PARTITIONS</literal> or
             <literal>SUBPARTITIONS</literal> clause. Beginning with this
             version, this value must adhere to the following rules:


Modified: branches/telcos/refman-5.1/versions.ent
===================================================================
--- branches/telcos/refman-5.1/versions.ent	2006-12-23 06:37:20 UTC (rev 4336)
+++ branches/telcos/refman-5.1/versions.ent	2006-12-23 06:52:41 UTC (rev 4337)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 804 bytes

@@ -7,5 +7,5 @@
 <!ENTITY current-series "5.1"><!-- Current MySQL release series  -->
 <!ENTITY previous-series "5.0"><!-- Previous MySQL release series  -->
 <!ENTITY next-series "5.2"><!-- Next MySQL release series  -->
-<!ENTITY current-version "5.1.12-beta"><!-- Current MySQL Version - update with new releases -->
+<!ENTITY current-version "5.1.14/NDB-6.1.0-beta"><!-- Current MySQL Version - update with new releases -->
 <!ENTITY current-maturity "beta"><!-- Current maturity level: alpha, beta, release candidate, production  -->


Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-12-23 06:37:20 UTC (rev 4336)
+++ trunk/refman-5.1/partitioning.xml	2006-12-23 06:52:41 UTC (rev 4337)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 688 bytes

@@ -4717,7 +4717,7 @@
         
         <para>
           If, when creating tables with a very large number of
-          partitions (but which isless than the maxmimum stated
+          partitions (but which is less than the maxmimum stated
           previously), you encounter an error message such as
           <errortext>Got error 24 from storage engine</errortext>, this
           means that you may need to increase the value of the