Bug #21240 Backup on Mysql administrator fails to backup essential information schema data

• Submitted: 23 Jul 2006 16:41
• Modified: 24 Jul 2006 7:13
• Reporter: Charlie Farrow
• Status: Duplicate
• Category: MySQL Administrator
• Severity: S2 (Serious)
• Version: 1.1.9
• OS: Windows (Win XP SP2)
• CPU Architecture: Any

[23 Jul 2006 16:41] Charlie Farrow

Description:
The backup facility in mysql administrator fails to backup triggers and stored proceedures associated with the database, causing an incomplete backup to be performed and hence an inability to restore the database.

In the backup i performed, every stored proceedure had the following  lines in the backup file:

--
-- Function `wpdb2`.`value_sets_in_job`
--

DROP FUNCTION IF EXISTS `value_sets_in_job`;
DELIMITER $$

 $$

But there were no lines to create the function.

Backing up the information schema table is not always the answer, because when mysql is running several databases, you would not want to overwrite the information schema tables in the event of the failure of one database.

Thefore on database dump, i think the correct behavior is for the triggers and stored procs to be backuped with the database, you should not have to backup the information schema tables also as it might not be possible to restore them (due to not wanting to overwrite other data)

How to repeat:
Try using mysql administrator to dump and then restore the tables when they have triggers and stored proceedures.

Suggested fix:
When dumping a database, it should also pull metadata from the infomation schema on these tables.

[24 Jul 2006 7:13] Sveta Smirnova

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicates Bug #15555.

Also I can backup functiom correctly.