How can we help you today? How can we help you today?

Comparison keeps flagging index changes

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?
bstewart
0

Comments

7 comments

Sort by
  • Michael Christofides
    Thanks for the report. Could you check you're using the latest version (Help -> Check for updates) and if not update and try again.

    Apologies for the inconvenience, I'll look into whether this is something we thought we'd fixed.
    Michael Christofides
    0
  • bstewart
    Sorry, I should have mentioned the version number. 1.0.0.409 which should be the latest version (running on Win 7 Enterprise SP1 x64).
    bstewart
    0
  • Michael Christofides
    No problem, thank you.

    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
    Michael Christofides
    0
  • helrod
    I see the exact same issue. Also running 1.0.0.409 (trial). Also running Windows 7 64-bit. Against MSSQL

    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.
    helrod
    0
  • Michael Christofides
    Thanks for letting us know helrod, I'll update here when we have a fix available.

    When you say "Against MSSQL", what do you mean? I've normally seen this as the abbreviation of Microsoft SQL Sever.
    Michael Christofides
    0
  • Michael Christofides
    Thanks all for your patience, this issue has now been fixed. You can get the latest versions by checking for updates within the tool or from our website here:
    http://downloads.red-gate.com/MySQLComparisonBundle.exe
    Michael Christofides
    0
  • bstewart
    Thanks all for your patience, this issue has now been fixed. You can get the latest versions by checking for updates within the tool or from our website here:
    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.
    bstewart
    0

Add comment

Please sign in to leave a comment.