Bug #49612 After de-selecting tables from a backup project, they are still backed up
Submitted: 11 Dec 2009 6:54 Modified: 11 Dec 2009 16:12
Reporter: Scott Rosenberg Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.2.17 OS:Windows (XP SP3)
Assigned to: CPU Architecture:Any
Tags: Backup

[11 Dec 2009 6:54] Scott Rosenberg 
Description:
In the "Backup Project" tab, if some tables are de-selected (unchecked) in the "Backup Content" tree view those tables are still backed up on execution.

I used the S2 severity because this can be a blocker to the end user if the tables that they're trying to skip are multiple gigs and exceed storage on the client (or time constraints of the user).

This bug was not present in 1.2.9 (was doing backups this way for months in that version).  I am not sure about intermediate versions.

How to repeat:
1) Click "Backup" -> "New Project".

2) Select the "mysql" DB (or any other DB on the system).

3) Click the ">" button.

4) De-select (uncheck) the "proc" object.

5) Click "Execute Backup Now".

6) Save the backup file to any valid location.

7) Open the backup file in any text editor and search for "CREATE TABLE `proc`".

Suggested fix:
Enable check boxes to control the backup of objects.
[11 Dec 2009 10:09] Valeriy Kravchuk 
This is a duplciate of bug #44762.
[11 Dec 2009 10:25] Susanne Ebrecht 
This is not repeatable with Workbench 5.2.10.
[11 Dec 2009 16:12] Scott Rosenberg 
Apologies for the dupe.  I did search beforehand, but must have missed it.