Bug #43085 misleading error message
Submitted: 21 Feb 2009 23:33 Modified: 25 Feb 2009 12:25
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.16 (acc. to help..about OS:Any
Assigned to: Mike Lischke CPU Architecture:Any
Tags: qc

[21 Feb 2009 23:33] Peter Laursen
see image.

A dump created with SQLyog raises this error with restore in MA (but strange enough QB can handle it!)

How to repeat:
see above

Suggested fix:
There are dozens of applications. Webbased tools, GUI clients, backup routines integrated in applications.  MA will never know them all. 

Error message could be:
" .. was created by another application using syntax not supported by this aapplication.!

But I am not able to understand why MA simply does not execute the statements in the file!
[21 Feb 2009 23:34] Peter Laursen
error when importing dump created by sqlyog

Attachment: dump.jpg (image/jpeg, text), 35.80 KiB.

[23 Feb 2009 8:17] Valeriy Kravchuk
Thank you for the problem report.
[23 Feb 2009 13:40] Mike Lischke
I'm sorry. This is really a limitation of MA. In order to allow selective restoration of objects MA parses the content of the file. However, this old implementation uses regular expressions and hence is not able to cope with all possible SQL variants, which could be thrown at it. So it does a weak protection by checking the header of the file to find a copyright string in there and refuses to restore such a file by default.

However, you have several possibilities to get around this:

1) Create the backup with MA instead SQLyog.
2) Look at another backup created by MA and copy the one line which is missing in the header and refers to MA into the other dump from SQLyog.
3) Load and execute the dump in Query Browser.
4) Load and execute the dump in mysql (the CLI).
5) Set the "Ignore Errors" check box on the General tab in the restore dialog.
[23 Feb 2009 14:55] Peter Laursen
Couldn't you possible fix the error message! That was all I asked! I know about MA incompabilities!

For instance "This dump was created with mysqldump or a third party application" for instance!

Of course the ultimate solution always is to use SQLyog! But that is not the discussion. And btw. the dump created with SQLyog will start like this

SQLyog Enterprise - MySQL GUI v6.16 RC
MySQL - 5.0.45-Debian_1ubuntu3.3-log : Database - acting_agent_base

.. so there is no reason why it should be confused with mysqldump!
[23 Feb 2009 15:05] Mike Lischke
I see what you mean. I wasn't aware that we just print out "... created by mysqldump...", which is rather stupid, given the number of tools which can create dumps. If it is only about the error message, this can be fixed easily. Just not the parsing.
[23 Feb 2009 15:18] Peter Laursen
[25 Feb 2009 12:25] Mike Lischke
Fixed in repostory administrator, revision 410