From: jon
Date: March 10 2006 3:48am
Subject: svn commit - mysqldoc@docsrva: r1546 - trunk/refman-5.1
List-Archive: http://lists.mysql.com/commits/3679
Message-Id: <200603100348.k2A3mN3I000484@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-03-10 04:48:22 +0100 (Fri, 10 Mar 2006)
New Revision: 1546

Log:

Partitioning and NULL: Couple of afterthoughts.



Modified:
   trunk/refman-5.1/partitioning.xml

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-03-10 02:11:17 UTC (rev 1545)
+++ trunk/refman-5.1/partitioning.xml	2006-03-10 03:48:22 UTC (rev 1546)
@@ -2008,6 +2008,11 @@
 mysql&gt; <userinput>SELECT * FROM t2;</userinput>
 Empty set (0.00 sec)
 </programlisting>
+      
+      <para>
+        (For more information on <literal>ALTER TABLE ... DROP
+          PARTITION</literal>, see <xref linkend="alter-table"/>.)
+      </para>
 
       <para>
         Such treatment also holds true for partitioning expressions that
@@ -2153,6 +2158,12 @@
       </para>
       
       <para>
+        As shown earlier in this section, you can also verify which
+        partitions were used for storing the values by deleting them and
+        then performing a <literal>SELECT</literal>.
+      </para>
+      
+      <para>
         <literal>NULL</literal> is handled some what differently for
         tables partitioned by <literal>HASH</literal> or
         <literal>KEY</literal>. In these cases, any partition expression