Bug #69467 Export recordset to an external file overwrites existing file
Submitted: 14 Jun 2013 7:39 Modified: 31 Jul 2013 15:26
Reporter: Jan T. Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2, 6.0.2 OS:Any
Assigned to: CPU Architecture:Any

[14 Jun 2013 7:39] Jan T.
Description:
The function "Export recordset to an external file" does not check for existing files with the same name. Instead, the file is overwritten without any warning.

How to repeat:
* Select rows from a table
* Try to export the recordset by using the red export icon
* Choose a filename that already exists in the selected folder
[14 Jun 2013 7:40] Jan T.
Spelling
[14 Jun 2013 8:03] MySQL Verification Team
Hello Jan T,

Thank you for the report.
Verified as described.

Thanks,
Umesh
[31 Jul 2013 15:26] Philip Olson
Fixed as of MySQL Workbench 6.0.4, and here's the changelog entry:

The "Export recordset to an external file" option would not check for
existing files with the same name, and would overwrite a file without
providing a warning. A prompt is now generated that asks if you want to
overwrite the existing file.

Thank you for the bug report.