Bug #76427 Export to Dump Project Folder
Submitted: 22 Mar 2015 1:16 Modified: 22 Mar 2015 8:36
Reporter: Kamal Doublani Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.2.4 OS:Windows (Microsoft Windows 8.1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[22 Mar 2015 1:16] Kamal Doublani
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\kamal\AppData\Roaming\MySQL\Workbench\log\wb.log]
Export to Dump Project Folder: Not Working, the massage box is shown with error message.

How to repeat:
Try to export your database using Administration - Data Export then choose Export to Dump Project Folder in Export Options

Suggested fix:
In the file wb_admin_export.py in modules folder, go to the line number 1712, do the same for the line 1715 (change args.append['--skip-triggers'] to args.append('--skip-triggers') and args.append['--no-create-info'] to args.append('--no-create-info'))
[22 Mar 2015 1:18] Kamal Doublani
Wb Log

Attachment: wb.log (application/octet-stream, text), 22.90 KiB.

[22 Mar 2015 8:36] MySQL Verification Team
Hello Kamal Doublani,

Thank you for the report.
This is most likely duplicate of Bug #74967 which is fixed as of the upcoming MySQL Workbench 6.2.5 release, and here's the changelog entry:

Executing "Data Export" against multiple databases with the "Export to
Dump Project Folder" option enabled would fail and generate an unhandled
exception; "Error Unhandled exception: 'builtin_function_or_method' object
has no attribute '__getitem__'". 

As a workaround, an export with the "Export to self-contained file" 
option functioned properly.

Thank you for the bug report.

Thanks,
Umesh