Bug #52689 version of mysqldump unclear
Submitted: 8 Apr 2010 12:35 Modified: 10 May 2010 14:34
Reporter: Susanne Ebrecht Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version: OS:Any (Linux, Mac)
Assigned to: Alfredo Kojima CPU Architecture:Any

[8 Apr 2010 12:35] Susanne Ebrecht
Per default Workbench takes mysqldump from client machine.

But often server is remote.

Means remote server can have different version then mysqldump on local machine.

But which version does this mysqldump have?

What if dump is for server version 5.0 and user wants to dump server 5.1?
What if dump is for server version 5.1 and user wants to dump server 5.0?

We have to make sure here that when user is dumping server 5.1 that then mysqldump for server 5.1 is taken and not an older version.

By default and not changeable from the user are mysqldump options like
--events and --replace

These options are only available in mysqldump 10.13 (Server 5.1) and not in mysqldump 10.11 (Server 5.0).

How to repeat:
Look what is taken when you try to use Workbench to dump data.

Suggested fix:
Either you will check mysqldump already during installation and stop installation and inform the user if mysqldump is too old.

Or you check mysqldump when user will try to dump the first time. If version too old then inform the user.
[8 Apr 2010 14:04] Mike Lischke
Susanne, I don't really get what you are after here. A user can already use his local mysqldump tool (regardless of the local version) to dump a schema from a remote (or local) server. This has nothing to do with WB. Except for a bug like Bug #30123 mysqldump does not so much depend on the actual server version. There might be cases where, say, a very old mysqldump version is used to dump a schema from a very new server, but this is not the problem of WB (not to mention that we ship the latest stable mysqldump version, not the oldest).
[9 Apr 2010 3:48] Alfredo Kojima
Indeed, remote mysqldump is never used. I believe this should be marked Not a bug.
[27 Apr 2010 14:17] Alfredo Kojima
Mea culpa, I misunderstood the description.

A check for the mysqldump version and comparison to the server version is now made.
If minor version is older than server, it will show a warning about the situation in the logs.
If user still clicks Start backup a popup dlg with the same warning will be shown and will confirm
whether the user wants to continue anyway.
[10 May 2010 13:35] Johannes Taxacher
fix confirmed in repository
[10 May 2010 14:34] Tony Bedford
A 'change' entry has been added to the 5.2.21 changelog:

MySQL Workbench now features a check that compares the version of mysqldump on the client and server machines.