From: jon
Date: November 26 2006 8:58am
Subject: svn commit - mysqldoc@docsrva: r4032 - trunk/refman-5.1
List-Archive: http://lists.mysql.com/commits/15821
Message-Id: <200611260858.kAQ8wcex025971@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Author: jstephens
Date: 2006-11-26 09:58:38 +0100 (Sun, 26 Nov 2006)
New Revision: 4032
Log:
Fixes Docs Bug #24439
Modified:
trunk/refman-5.1/partitioning.xml
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-11-25 18:04:07 UTC (rev 4031)
+++ trunk/refman-5.1/partitioning.xml 2006-11-26 08:58:38 UTC (rev 4032)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 8; 1774 bytes
@@ -4028,14 +4028,18 @@
This type of optimization can be applied whenever the partitioning
expression consists of an equality or a range which can be reduced
- to a set of equalities. It can also be employed when the
- partitioning expression represents an increasing or decreasing
- relationship or uses a function such as YEAR()
- or TO_DAYS() that produces an integer value
- when applied to a DATE or
- DATETIME column value. For example, suppose
- that table t2, defined as shown here, is
- partitioned on a DATE column:
+ to a set of equalities, or when the partitioning expression
+ represents an increasing or decreasing relationship. Pruning can
+ also be applied for tables partitioned on a DATE or
+ DATETIME column when the partitioning
+ expression uses the YEAR() or
+ TO_DAYS() function.
+ (Note: We plan to add pruning
+ support in a future MySQL release for additional functions that
+ act on a DATE or DATETIME
+ value, return an integer, and are increasing or decreasing.) For
+ example, suppose that table t2, defined as
+ shown here, is partitioned on a DATE column: