Maybe. But if I click on the ellipsis, the Windows dialog has CSV preselected in
Save as type, even if the prior extension isn't CSV.
But even more strongly, all the settings on the Export data to file dialog are CSV-compliant except that one. Shouldn't common standards be the default? What value is there in being "almost" CSV vs. being truly CSV?
The problem with this is when you save a CSV with semicolons instead of commas, other programs may not recognize the file. Already ran into a problem importing into Excel with semicolon separations. So if I forget change to comma, I may end up doing an export and may risk a complex CSV edit later. (It's simple if you're just replacing ";" with "," but can be complex in certain scenarios.)
Aren
On Sat, Nov 6, 2010 at 4:19 PM, Thom Brown
<thom@linux.com> wrote:
On 6 November 2010 21:08, Aren Cambre
<aren@arencambre.com> wrote:
Bug report:
When I use File > Export from a Query window, it's clearly trying to make a CSV. The suggested filename is suffixed with .csv.
Are you sure that isn't just there because that's the last filename you used? Mine doesn't default to anything. If I click on the ellipsis and type a filename without an extension into the file browser and click OK, it just comes up with the path and the filename I typed without an extension.
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
