Re: Partitioned table problem after upgrade to 5.5

[Ming Wang]

hi Mattias Jonsson

the table is Linear Key partitioned and using a BIGINT column to do this partition.

and the partition key is only the BIGINT column.

because of my table size, i am tring to rebuild and optimize the table in 5.5, and it will cost lots time.

SHOW CREATE TABLE:
CREATE TABLE `Table.Name` (
`ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`String_Column_1` varchar(255) CHARACTER SET utf8 NOT NULL,
`BIGINT_Column_1` bigint(20) unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (`ID`,`BIGINT_Column_1`) USING BTREE,
UNIQUE KEY `unique_Channel_ID_URL` (`BIGINT_Column_1`,`String_Column_1`) USING BTREE,
KEY `index_String_Column_1` (`String_Column_1`),
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
/*!50100 PARTITION BY LINEAR KEY (BIGINT_Column_1)

The query is:
select * from Table.Name where BIGINT_Column_1=XXXXXXX and String_Column_1="WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW"; --- No result return
select * from Table.Name where ID=XXXX--- get the result return
there is one record:
ID:XXXX
BIGINT_Column_1:XXXXXXX
String_Column_1:WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
by right, these 2 query should find the same record.
THANKS.