Bug #78756 Workbench CSV Export doesn't export CSV
Submitted: 8 Oct 2015 12:14 Modified: 12 Oct 2015 7:01
Reporter: Lee Butler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.4.0 (maybe earlier) OS:Windows (10, but appears on others)
Assigned to: CPU Architecture:Any
Tags: csv, export, workbench

[8 Oct 2015 12:14] Lee Butler
Description:
The CSV (comma separated values) function for exporting data from a table in Workbench, when provided with options for the field separators, does not offer the use of a comma. The Comma Separated Values export wizard doesn't Separate Values by Comma, and there isn't an option to.

For people who want to export the data for use in another application, like I use data for Excel, which (understandably) only reads fields separated by commas, this is very annoying, as I tend to export it with Semicolons (the default option) then open the CSV in Notepad++, find and replace and then save it again before opening in Excel.

How to repeat:
1. Open any schema in workbench

2. Right click a table in the schemas part of the navigation pane.

3. Open Table Data Export Wizard

4. Choose columns and press next

5. Ensure the csv radio button is checked

6. Press the "Field Separator" drop down

LOOK, No commas.

Suggested fix:
Add a comma into the field separator drop down, and set it as the default option, as this is the generally accepted field separator foe CSVs. Refer to RFC 4180 for more details (Although not a formal standard, it documents common practice which the application should at least provide the option for.
[8 Oct 2015 21:41] MySQL Verification Team
Thank you for the bug report. Alright there is the semicolon option as separator which works with Excel too but no comma option.
[9 Oct 2015 9:16] Lee Butler
Semicolons don't work in Office 2013

Attachment: nosemi.png (image/png, text), 70.37 KiB.

[12 Oct 2015 7:01] Marcin Szalowicz
Fixed as of the upcoming MySQL Workbench 6.3.5 release, and here's the
changelog entry:

In the Table Data Import wizard, the Field Separator dropdown in the
Configure Import Settings operation did not list the "," (comma)
character.