MySQL Bugs: #58064: Consider updating the 5.5 introduction to partitioning

Bug #58064	Consider updating the 5.5 introduction to partitioning
Submitted:	8 Nov 2010 21:12	Modified:	10 Nov 2010 18:22
Reporter:	Lenz Grimmer	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.5	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	5.5, documentation, partitioning

Description:
The introduction chapter about Partitioning in MySQL 5.5 is still focused on just using integer values for the partitioning function:

http://dev.mysql.com/doc/refman/5.5/en/partitioning.html

" This expression can be either an integer column value, or a function acting on one or more column values and returning an integer. The value of this expression is passed to the partitioning function, which returns an integer value representing the number of the partition in which that particular record should be stored. This function must be nonconstant and nonrandom. It may not contain any queries, but may use an SQL expression that is valid in MySQL, as long as that expression returns either NULL or an integer intval such that

-MAXVALUE <= intval <= MAXVALUE
(MAXVALUE is used to represent the least upper bound for the type of integer in question. -MAXVALUE represents the greatest lower bound.)"

I wonder if this is still correct in the case of MySQL 5.5, which support partitioning tables on types other than integers?

How to repeat:
Take a look at the partitioning chapter, determine if the explanation is still accurate/up to date for MySQL 5.5.

Thank you for the bug report.

This one has my name written all over it. :)

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.