Bug #26719 Error during FEDERATED engine creation

• Submitted: 28 Feb 2007 13:12
• Modified: 31 May 2007 15:24
• Reporter: Victoria Reznichenko
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S2 (Serious)
• Version: 5.0.38
• OS: Any (any)
• Assigned to: MC Brown
• CPU Architecture: Any
• Tags: bfsm_2007_03_15

[28 Feb 2007 13:12] Victoria Reznichenko

Description:
During FEDERATED engine creation I've got error:

ERROR 1089 (HY000): Incorrect sub part key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique sub keys

MyISAM table with exactly the same structure was created just fine, there is nothing about limitation on indexes in this section of the manual:
http://dev.mysql.com/doc/refman/5.0/en/federated-limitations.html

How to repeat:
Created FEDERATED engine with structure listed below.

[2 Mar 2007 10:21] Magnus Blåudd

"Created FEDERATED engine"? Do you mean "Create table in FEDERATED engine"?

[2 Mar 2007 10:25] MySQL Verification Team

sure.

[4 Mar 2007 14:34] MySQL Verification Team

smaller testcase to show the problem:

on remote host
---------------
drop table if exists `t1`;
create table `t1`(`a` varchar(100),unique key(`a`(30)))engine=myisam;

on localhost
--------------
drop table if exists `t1`;
create table `t1`(`a` varchar(100),unique key(`a`(30))) engine=federated connection='mysql://127.0.0.1:3306/test/t1';

the last statement returns "ERROR 1089 (HY000): Incorrect sub part key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique sub keys"

[31 May 2007 15:24] MC Brown

The manual has been updated to note the limitation with indexes on Federated tables (in particular the prefix index issue on CHAR/TEXT/BLOB columns), plus a general note about index compatibility between federated and other engine types.