Hello -
I have used mysqldiff. I agree with the comments in the bug report
part of which is copied at the end. Among other things, the comment said:
"it's completely useless as it is, mysqldiff produces imaginary
diffs dropping all the keys just because mysql decides to output
keys in create table in different order"
And from the response of developers is very stiff.
- Is there any hope to make this tool useful?
- What is the difference between mysqldiff and mysqldbcompare?
Looks like the latter is an old version of mysqldiff.
- Is there any other tools that can be used to serve the same purpose,
either GUI or command line, free or commercial? Redgate's mysql compare
does the job, but I was told that they are dropping the development
and support to concentrate on MS SQL.
Thanks.
http://bugs.mysql.com/bug.php?id=65169
[26 Apr 20:57] Charles Bell
Fixed in release-1.2.2.
[3 May 5:02] Philip Olson
Fixed as of the upcoming MySQL Utilities 1.2.2, and here's the
changelog entry:
The "mysqldiff" utility would consider two tables as different if the
columns or indexes were ordered differently.
Thank you for the bug report.
[22 May 9:01] Ricardo Oliveira
This bug is not fixed. I can reproduce it on:
MySQL Utilities mysqldiff version 1.3.1 (part of MySQL Workbench
Distribution 5.2.47) on ubuntu 12.04 (compiled from source)
--changes-for argument will bring back all the wrong diffs based on order of statements. Also it seems you guys still didnt get this right. If server1 has table t1 and server2 does not, the output show show the sql statement creating table t1, just like the GUI version does. As it is right now, the command line tools are pretty useless.
[5 Sep 7:08] Ricardo Oliveira
is anyone still maintaining this code? it's completely useless as it is, mysqldiff produces imaginary diffs dropping all the keys just because mysql decides to output keys in create table in different order
I have used mysqldiff. I agree with the comments in the bug report
part of which is copied at the end. Among other things, the comment said:
"it's completely useless as it is, mysqldiff produces imaginary
diffs dropping all the keys just because mysql decides to output
keys in create table in different order"
And from the response of developers is very stiff.
- Is there any hope to make this tool useful?
- What is the difference between mysqldiff and mysqldbcompare?
Looks like the latter is an old version of mysqldiff.
- Is there any other tools that can be used to serve the same purpose,
either GUI or command line, free or commercial? Redgate's mysql compare
does the job, but I was told that they are dropping the development
and support to concentrate on MS SQL.
Thanks.
http://bugs.mysql.com/bug.php?id=65169
[26 Apr 20:57] Charles Bell
Fixed in release-1.2.2.
[3 May 5:02] Philip Olson
Fixed as of the upcoming MySQL Utilities 1.2.2, and here's the
changelog entry:
The "mysqldiff" utility would consider two tables as different if the
columns or indexes were ordered differently.
Thank you for the bug report.
[22 May 9:01] Ricardo Oliveira
This bug is not fixed. I can reproduce it on:
MySQL Utilities mysqldiff version 1.3.1 (part of MySQL Workbench
Distribution 5.2.47) on ubuntu 12.04 (compiled from source)
--changes-for argument will bring back all the wrong diffs based on order of statements. Also it seems you guys still didnt get this right. If server1 has table t1 and server2 does not, the output show show the sql statement creating table t1, just like the GUI version does. As it is right now, the command line tools are pretty useless.
[5 Sep 7:08] Ricardo Oliveira
is anyone still maintaining this code? it's completely useless as it is, mysqldiff produces imaginary diffs dropping all the keys just because mysql decides to output keys in create table in different order