MySQL Bugs: #23365: Error message "The dump file was not created with MySQL Admin"

Bug #23365	Error message "The dump file was not created with MySQL Admin"
Submitted:	17 Oct 2006 11:43	Modified:	17 Oct 2006 12:38
Reporter:	Ulrich Riedel	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.4 rc	OS:	Windows (Windows XP SP2)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Trying to restore a backup (made with admin 1.1.x) with target schema = Original Schema, Backup Type = SQL Files, Ignore Erros = Off, Create Database if don't exist = On, returns the error message 'The dump file was not created with MySQL Administrator. Currently only such dumps can also be restored' during analyze phase.
Switching Ignore Errors to On returns a warning with the hint 'The dump file was not created with MySQL Administrator. Results are unpredictible' during analyze phase.
With Ignore Errors = On the restore is working fine.
It occures with server 4.1.21-community-nt and 5.0.24a.

How to repeat:
Take a backup made with a 1.4.x version of MySQL Administrator, settings like described above.
I got the same result with different backup files.
I got the same result with admin of boundle mysql-gui-tools-5.0-r3-win32.msi and  mysql-gui-tools-5.0-r4-win32.msi.

We are sorry but this problem cannot be fixed because the identification string used to determine if the dump was made by MA has been introduced later (I think in 1.2) so we are unabled to detect dumps made before that version. However since you can ignore errors there is no harm to your data. You should still be able to restore from the dump files. And since it is a valid MA dump you should not see any difference except for the warning.

If this warning appears to often to you then you can redo your dump with the latest MA version. Or you can manually adjust the header in the SQL dump using an editor of your choice. For the latter just see how the current header looks which MA produces now.