Options
Comparison keeps flagging index changes
bstewart
Posts: 12
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:
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?
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
Apologies for the inconvenience, I'll look into whether this is something we thought we'd fixed.
I'm afraid it looks like its an bug we'll need to fix in the tool. Please do let me know if you're evaluating or an existing customer. Feel free to email us at mysql@red-gate.com
It's kind of a deal-breaker, as in this schema, I get about 200 false positive changes because there's an index -- even though the index is identical. Toad doesn't seem to have this problem.
When you say "Against MSSQL", what do you mean? I've normally seen this as the abbreviation of Microsoft SQL Sever.
http://downloads.red-gate.com/MySQLComparisonBundle.exe
I downloaded the latest version (1.0.0.425) and the issue appears to be resolved. Thanks for the update Michael.