MySQL Bugs: #45245: Prefix indexes in MySQL Cluster

Bug #45245	Prefix indexes in MySQL Cluster
Submitted:	1 Jun 2009 13:12	Modified:	28 Aug 2009 13:48
Reporter:	Vinod Sugur	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S2 (Serious)
Version:	mysql-5.1-telco-7.0, 5.0	OS:	Any (Linux, Solaris sparc 64 bit)
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	5.1.32-ndb-7.0.5-cluster-gpl-log, MySQL cluster prefix index

Description:
MySQL cluster does not support prefix index but as per the below url it seems that this issue was resolved in MySQL cluster release 5.0.

http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-limitations-resolved.html
====================
Column indexes using prefixes.   MySQL Cluster in MySQL 5.0 supports column indexes that make use of prefixes. 
====================

How to repeat:
CREATE TABLE `test_ndb` (
  `v_col` varchar(199) DEFAULT NULL,
KEY `ix_test_ndb` (`v_col`(10))
) ENGINE=ndbcluster ;

show create table test_ndb;
+----------+-----------------------------------------------------------------------------------------------------------------------------------------+
| Table    | Create Table                                                                                                                            |
+----------+-----------------------------------------------------------------------------------------------------------------------------------------+
| test_ndb | CREATE TABLE `test_ndb` (
  `v_col` varchar(199) DEFAULT NULL,
  KEY `ix_test_ndb` (`v_col`)
) ENGINE=ndbcluster DEFAULT CHARSET=latin1 | 
+----------+-----------------------------------------------------------------------------------------------------------------------------------------+

Suggested fix:
This should be fixed.

Thank you for the report.

Verified as described.

But this is not documented in 5.1 manual, probably just 5.0 manual should be fixed.

Was wrong category.

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.