Bug #7358 | mysqldump: Simltanious use of --master-data & --single-transaction doesn't work | ||
---|---|---|---|
Submitted: | 16 Dec 2004 19:38 | Modified: | 18 Dec 2004 17:39 |
Reporter: | Shuichi Tamagawa | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: mysqldump Command-line Client | Severity: | S2 (Serious) |
Version: | 4.1.8 | OS: | Linux (SuSE Linux 9.0) |
Assigned to: | Guilhem Bichot | CPU Architecture: | Any |
[16 Dec 2004 19:38]
Shuichi Tamagawa
[18 Dec 2004 17:39]
Guilhem Bichot
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 bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: This is not a fatal error, just a warning, mysqldump still prints the CREATE DATABASE and continues dumping. What's new in 4.1.8 is that this warning is shown. Good thing, as it made us notice that since 4.1.7 there is a problem with SHOW CREATE DATABASE in mysqldump --single-transaction (no --master-data) --all-databases: if there are two databases, and first db has a non-empty InnoDB table, the SHOW CREATE DATABASE will fail on second db, so CREATE DATABASE will be printed but without the CHARACTER SET clause. I fix the failure of SHOW CREATE DATABASE (not due to my recent patches to mysqldump) and remove the warning display (due to my recent patches to mysqldump), in 4.1 in: ChangeSet@1.2086.165.1, 2004-12-17 23:37:43+01:00, guilhem@mysql.com