Bug #19030 | new backup without selecteed db's does not work as expected | ||
---|---|---|---|
Submitted: | 12 Apr 2006 7:03 | Modified: | 22 Aug 2006 10:29 |
Reporter: | Sebastian Mendel (Basic Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S2 (Serious) |
Version: | 1.1.9 | OS: | Windows (Windows XP) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
Tags: | Backup |
[12 Apr 2006 7:03]
Sebastian Mendel
[12 Apr 2006 8:12]
Valeriy Kravchuk
Verified just as described. In my case (XP Home Edition) I've got Access violation when clicking on "Complete Backup", but, after clicking OK, I saw the check box checked and was able to save backup project. Anyway, this access violation is surely a bug to be fixed.
[22 Aug 2006 9:29]
Mike Lischke
"Complete Backup" refers to all tables in all selected schemas, that is, schemas that are listed in the content tree. It does not mean all schemas on the server are backuped up. I'm going to fix the access violation though.
[22 Aug 2006 10:29]
Mike Lischke
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html