Re: Improper CSV export delimiter

Le 06/11/2010 23:13, Aren Cambre a écrit :
> 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.
>

Because it's the first one in the list of "often used" extensions. We
don't really *want* it to be preselected. It happens to be so because
it's the first item of the list.

> 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?

Yes.

> What value is there in being "almost" CSV vs. being truly CSV?
>

None.

Except that everyone has his definition of CSV. Mine would be to use
comma (hence the acronym :) ). Others don't have the same feelings.

> 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.)
>

I don't know for new ones as I don't use Excel these days. Old Excel
releases always wanted to use ";" instead of "," for CSV files.

Which is not a good enough reason to use ";" instead of ",".

It would be interesting to review this dialog.

--
Guillaume
http://www.postgresql.fr
http://dalibo.com