MySQL Bugs: #43390: MySQL Administrator backups full schema, not only selected tables

Bug #43390	MySQL Administrator backups full schema, not only selected tables
Submitted:	4 Mar 2009 18:50	Modified:	19 Oct 2009 7:01
Reporter:	Carlos Amengual	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.17	OS:	Windows (Windows XP Professional x64 edition)
Assigned to:		CPU Architecture:	Any
Tags:	CHECKED

Description:
After making a backup project that contains, for example, only one table from a schema, MySQL Administrator, executing such project will backup the whole schema, instead of the single table that was intended.

This did not happen with previous versions of Administrator (bug is present in 1.2.17, was not in 1.2.16).

How to repeat:
Open Administrator, click on "Backup" icon, create a new project, select a schema and then click on the ">" button. The tables of the schema appear at right.

Then click next to the schema name to deselect all tables, and just click on a single table to select it. Click on "Save project" and then on "Execute backup now".

The resulting file contains a backup for all tables in schema.

Thank you for the bug report.

Hello,

Just for info, I noticed the same.

Very annoying, particularly if the schema also contains other big tables.

I think this problem is new / recent. Almost sure it did work up to recently.

Louis

Administrator's backups are sometimes used to deliver tables from the development server to production. If you only want to save a couple tables at the development server, and then restore these at the production database, this bug may result in data loss (production data replaced by development stuff).

The bug is just annoying for those who are aware of it, but could be a major one otherwise.

Hello,

"MySQL" could you please fix this bug on short terms !!

IMHO it is perhaps not creatical for the database as a whole,
but it is that severire that I am going back to the previeus version
of MySQL administrator. Can not live with it !!

Sincerely,

Louis

Don't know if it will help others, but. There is an option on the second tab "advanced options" - complete backup, and it's on by default. It works fine for me.

But it's EXTREMELY annoying!!! I create new project, select tables i want to backup on developer machine, backup's done without any notice that it's a complete backup. And on restore production tables that i was not about to rewrite get rewritten.

Hour ago i've killed production DB this way, [censored]!

Previous comment proves that this bug is in the "production database wipe-out" category.

And yes, it seems that fixing this bug amounts to reverting a dumb boolean default that breaks POLA (http://en.wikipedia.org/wiki/Principle_of_least_astonishment).

Boris you living legand, that worked!

This begs the question of why a full schema backup is selected as default by two functions in two different tabs?

Obviously checkaging of the every tickbox states that the user wants to backup the whole thing, and should be the default option. The average (and advanced) user would expect that deselecting all checkboxes and selecting the one table would mean that only that one would be backed up. To mean this is a simple requirement.

There is little point in having a "Complete Backup" option as well, and even less point in it being in another tab!

Perhaps it should be deselected by default or moved to the initial tab.

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench. We won't fix this anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/

After deselecting the checkbox, I was able to do backups on select folders. It is odd that the box is checked by default.