| Bug #54302 | Export annoyances | ||
|---|---|---|---|
| Submitted: | 7 Jun 2010 18:27 | Modified: | 18 Jun 2010 13:37 |
| Reporter: | Todd Farmer (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
| Version: | 5.2.22 | OS: | Windows (XP) |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[14 Jun 2010 14:39]
Alfredo Kojima
Changed CSV_tab export format name to Tab, use .tab file extension
[16 Jun 2010 21:29]
Johannes Taxacher
fix confirmed in repository
[18 Jun 2010 13:37]
Tony Bedford
An entry has been added to the 5.2.23 changelog: In the SQL Editor, when exporting a resultset to a TAB delimited file, MySQL Workbench added a .CSV extension.
Description: I tried to export a result set using WB. I wanted tab-separated data, so I chose "CSV (tab-delimited)". That's a strange label for tab-delimited, but I figured out why later: despite naming it "something.tab", WB appends the .csv extension (resulting in "something.tab.csv"). This is annoying, since .tab opens just fine in Excel, while .csv does not (for tab-delimited data). Anyhow, I changed the file back to be "something.tab", but had to export again. This time, I thought I would be smart, and select the actual file ("something.tab") using the file selector. It asked for confirmation before overwriting "something.tab" (which I granted), but then created "something.tab.csv" again, anyways. :( I note also that there is no file extension filter in the file dialog. It might be nice if it had various options appropriate for the output format previously selected. How to repeat: See above. Suggested fix: Don't append .csv extension, give appropriate options for output format previously selected.