Index algorithm not compared

[erikav]

It appears as if the index algorithm isn't considered when comparing table schemas. Is this something that can be added?

[alexa]

Could you please let us know what you mean by 'index algorithm'? In case you were referring to Index Type, dbForge can handle them, however, default values are not displayed in the definitions.

[erikav]

Here's a snippet from "SHOW CREATE TABLE", from two servers:

Server 1:
...
PRIMARY KEY (`GameID`,`WorldID`,`ClanGUID`,`CharacterID`) USING BTREE

Server 2:
...
PRIMARY KEY (GameID, WorldID, ClanGUID, CharacterID)


These appear to be considered equal by schema compare.

[alexa]

Could you please provide us the full CREATE definitions of the compared tables and the options that you had selected on the 'Options' page of the New Schema Comparison wizard?

To make sure your data is kept confidential, please send a reply straight to our support system at supportATdevartDOTcom, and we will keep further correspondence with you on this issue via that system.

[alexa]

We were able to reproduce this issue and will fix it in one of the next builds of the product. We will notify you once it's available for downloading.

[alexa]

We would like to let you know that we have released dbForge Studio for MySQL, v.6.1 beta where the issue you reported is fixed http://www.devart.com/news/2013/dbforge ... sql61.html

Thank you for your help in improving dbForge Studio for MySQL.