| Subject: | no support for USING BTREE |
Hi,
We are trying to use mysqldiff for maintaining database structure in a
project but are running in to some problems. When running show create
table for one of our tables we get this:
CREATE TABLE ...
...
`version` int(10) unsigned NOT NULL,
`server_id` int(10) unsigned NOT NULL default '0',
PRIMARY KEY USING BTREE (`id`,`server_id`),
KEY `Index_5` (`bidauctions_id`,`bid`),
KEY `Index_4` (`bidauctions_id`,`bid`,`bid_status`,`user_id`),
KEY `Index_2`
(`unique_`,`bid_status`,`bidauctions_id`,`bid`,`user_id`),
KEY `Index_3` (`bid`,`bidauctions_id`,`user_id`),
KEY `Index_9` (`mobile_id`),
KEY `Index_7` USING BTREE (`affiliate_campaign_id`),
KEY `Index_8` USING BTREE
(`affiliate_campaign_id`,`insert_timestamp`),
KEY `user_id` (`user_id`)
) ENGINE=InnoDB AUTO_INCREMENT=13849161 DEFAULT CHARSET=utf8
ROW_FORMAT=DYNAMIC;
The indexes called Index_7 and Index_8 seems to be causing an error in
Table.pm with the message: "definition for field `KEY' duplicated in
table ...".
Removing the USING BTREE from the mysqldump file removes this error but
since our live database gives us these when we run mysqldump we cannot
use mysqldiff.