Bug #102320 MySQL Workbench Export Fails if "Include Create Schema" Is Selected
Submitted: 20 Jan 2021 18:23 Modified: 21 Jan 2021 6:55
Reporter: Craig Bransfield Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:8.0 OS:Windows (10.0.19042 )
Assigned to: CPU Architecture:x86 (Intel Core-i7-3520M)

[20 Jan 2021 18:23] Craig Bransfield
Description:
When running Data Export with "Include Create Schema" selected, the following error occurs:

"Error executing task write() argument must be str, not bytes"

Export proceeds normally if "Include Create Schema" is not selected.

This problem occurs whether I use the mysqldump.exe included with Server installation, or the mysqldump.exe included with Workbench installation.

How to repeat:
Perform schema data export with option "Include Create Schema" selected (checked).
[20 Jan 2021 20:44] Craig Bransfield
Added OS/CPU info.
[21 Jan 2021 6:55] MySQL Verification Team
Hello Craig Bransfield,

Thank you for the bug report.
Verified as described.

Regards,
Ashwini Patil
[21 Jan 2021 6:58] MySQL Verification Team
8.0.23 test results

Attachment: 102320_test_results.png (image/png, text), 157.50 KiB.

[21 Jan 2021 7:20] MySQL Verification Team
Bug #102319 marked as duplicate of this one.
[22 Jan 2021 10:10] MySQL Verification Team
Bug #102342 marked as duplicate of this one.
[18 Mar 2021 15:28] Peter Fales
Bitten by the same bug.

When reported to stackoverflow (https://stackoverflow.com/questions/65830702/error-executing-task-write-argument-must-be-s...) suggested fixes include:

- Revert to 8.0.20 or earlier (I didn't try this)
- Don't check "Create Schema" (works, but messy)
- Make a code change to wb_admin_export.py (that did not work for me)
[22 Apr 2021 7:49] ulrich pfitzenmaier
Export from MySql workbench does not work neither for just data nor just schema!
[22 Apr 2021 7:49] ulrich pfitzenmaier
Export from MySql workbench does not work neither for just data nor just schema!
[15 Sep 2021 6:43] MySQL Verification Team
Bug #104936 marked as duplicate of this one.