MySQL Bugs: #70476: "The command line is too long." when exporting list of tables in Workbench

Bug #70476	"The command line is too long." when exporting list of tables in Workbench
Submitted:	1 Oct 2013 14:27	Modified:	16 Jun 2014 5:17
Reporter:	Bob Hansen	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	6.0.7.11215	OS:	Windows (Win7 Ultimate 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	database, export, failed, Operation, tables, workbench

Description:
I'm using Workbench trying to export a database to a self-contained SQL file. I select the database I want to export and select the tables I want to export (808 tables/views selected). I click Start Export and I get the error:

The command line is too long.

Operation failed with exitcode 1

09:07:34 Export of C:\Users\Bob\Documents\dumps\Dump20131001.sql has finished with 1 errors

How to repeat:
Export a large list of tables using Workbench.

Suggested fix:
This might require the same fix that was applied in the the data Migration wizard.

http://bugs.mysql.com/bug.php?id=66611

I tried changing my CLASSPATH to
C:\Windows\system32\cmd.exe /e:32768

but that didn't help. The actual command is 25813 characters long:

"mysqldump.exe --defaults-extra-file="c:\users\... ... "1112_contactlunchbalance_view"

Actual error I'm seeing

Attachment: command_line_too_long_error.png (image/png, text), 86.80 KiB.

One attempted workaround for the error

Attachment: command_line_too_long_comspec.png (image/png, text), 8.62 KiB.

Were all tables in the schema selected for export?

No, not all tables were selected. I'm guessing that there was somewhere around 900 tables in the database, 808 of which were selected for export.

Marking as duplicate of Bug #71799