Bug #59411 | mysqldump failure when exporting | ||
---|---|---|---|
Submitted: | 11 Jan 2011 6:14 | Modified: | 7 Feb 2011 15:26 |
Reporter: | Sidney van de Stouwe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.2.31 CE | OS: | Windows (window 7 64 bit) |
Assigned to: | CPU Architecture: | Any |
[11 Jan 2011 6:14]
Sidney van de Stouwe
[11 Jan 2011 6:42]
Sidney van de Stouwe
Just did some more checking and it apprears that it is caused by the location of --defaults-extra-file="d:\users\sidney~1\appdata\local\temp\tmpkeiszm". If I copy the log output to a mysqldump commandline it also failes. If I replace the extra file with --user=root --password=xxxxx it works fine. I therefore suspect that using the extra-file option has an error if the users directory is on a different drive then where the mysqldump.exe is residing I have tested the same output on a different computer where user directory is on the same drive as where mysqldump.exe is.
[11 Jan 2011 9:05]
Peter Laursen
59401 looks similar Peter (not a MySQL person)
[1 Feb 2011 13:11]
Johannes Taxacher
This is a result of a bug in mysqldump (Bug #59234) - we have added a workaround to workbench repository.
[7 Feb 2011 15:26]
Tony Bedford
An entry has been added to the 5.2.32 changelog: Running the version of mysqldump supplied with the MySQL Server package resulted in the following error: Operation failed with exitcode -1073741819