Bug #6597 Mysqladmin creates broken sqldumps
Submitted: 12 Nov 2004 15:49 Modified: 15 Nov 2004 10:57
Reporter: Daniel Tombeil Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.14 OS:Linux (Linux)
Assigned to: Bugs System CPU Architecture:Any

[12 Nov 2004 15:49] Daniel Tombeil
Description:
mysqladmin creats broken dumps while using the backup function. It uses double-quotes on the wrong positions in the dump:

DROP TABLE IF EXISTS `City`;
CREATE TABLE "City" (
                             ^^^^^^^^^^^
  "ID" int(11) NOT NULL auto_increment,
  ^^^^^^^^^

it also sets a comma and semicolon at the end of some lines where it should just be a semicolon.

 ('CAN','Eskimo Languages','F',0.1),
 ('CHN','Dong','F',0.2),
 ('RUS','Belorussian','F',0.3),
 ('USA','Portuguese','F',0.2),;
                                ^^^^^^^^^^^^^^

reimport fails until syntax is fixed.

How to repeat:
export a database via mysqladministrator (in my case the world demo database during a mysql course) using a profil with "Normal Backup"  and "Backup selected database completely" checked. In the "Output File Options" "Add drop table" is checked.

afterwards reimport fails an no real error message is provided in mysql-administrator. On the shell you can see the error message while importing the .sql file.

Suggested fix:
fixing export and maybe a better visible error message in mysql-administator
[15 Nov 2004 10:03] Andreas Götz
Can confirm this issue- backups are useless in 1.0.14...
[15 Nov 2004 10:57] MySQL Verification Team
Duplicate for #6594