What are the challenges you face when working across database platforms? Take the survey
Options

Comparison keeps flagging index changes

bstewartbstewart Posts: 12
edited December 11, 2012 4:47AM in MySQL Compare
I'm currently using a development database which is running the following MySQL version:

protocol_version;10
version;5.1.46-community
version_comment;MySQL Community Server (GPL)
version_compile_machine;unknown
version_compile_os;Win64

The UAT server I'm deploying to is as follows:

protocol_version;10
version;5.5.24-0ubuntu0.12.04.1
version_comment;(Ubuntu)
version_compile_machine;x86_64
version_compile_os;debian-linux-gnu

Whenever I do a compare between these two databases, any table with an index will get flagged as being changed. In the MySQL compare GUI when looking at the comparison between the CREATE statements for the two tables, the only difference is in the database prefix before the table name. However, the deployment script just contains a load of statements like this:
DROP INDEX `idx_usergroup_adjacency_lookup` ON `scie-uat`.`jos_usergroups`;
CREATE INDEX `idx_usergroup_adjacency_lookup` ON `scie-uat`.`jos_usergroups`(`parent_id`);
DROP INDEX `idx_usergroup_nested_set_lookup` ON `scie-uat`.`jos_usergroups`;
CREATE INDEX `idx_usergroup_nested_set_lookup` ON `scie-uat`.`jos_usergroups`(`lft`, `rgt`);
DROP INDEX `idx_usergroup_title_lookup` ON `scie-uat`.`jos_usergroups`;
CREATE INDEX `idx_usergroup_title_lookup` ON `scie-uat`.`jos_usergroups`(`title`);

Regardless of how many times I run the deployment, it always thinks those same tables have changes and generates similar DROP INDEX/CREATE INDEX statements in the deployment.

Any ideas how I can fix this?

Comments

Sign In or Register to comment.