Bug #52056 Creating unique index on blob/not null column of innodbplugin table throws error
Submitted: 15 Mar 2010 8:36 Modified: 15 Mar 2010 9:41
Reporter: Nirbhay Choubey Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB Plugin storage engine Severity:S3 (Non-critical)
Version:5.1.45, 5.5.1-m2, 5.5.3-m2 OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: regression

[15 Mar 2010 8:36] Nirbhay Choubey 
Description:
Creating a unique index on blob/text NOT NULL column of table created using
innodb-plugin throws the following error message :

100315 10:56:34 [ERROR] Table ./test/t1 has a primary key in InnoDB data dictionary, but not in MySQL!

While, I do not notice the same for innodb-builtin (on 5.1.xx). MyISAM works fine too.

Verified on 5.1.45, 5.1.44, & 5.5.1-m2

How to repeat:
DROP TABLE IF EXISTS t1;
CREATE TABLE t1(c1 LONGBLOB NOT NULL)ENGINE=INNODB;
CREATE UNIQUE INDEX i1 ON t1(c1(100));

However, are throwing the error message, table 't1' gets created, and further INSERT/SELECT seems to go normal.
[15 Mar 2010 9:08] Valeriy Kravchuk 
Thank you for the bug report. Verified just as described.
[15 Mar 2010 9:41] Valeriy Kravchuk 
Duplicate of Bug #51378 (still private) it seems.