| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: csv format for psql |
| Date: | 2018-03-31 08:44:29 |
| Message-ID: | e17b43c5-9950-ebca-8827-1fa6749ab143@archidevsys.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 31/03/18 21:33, Fabien COELHO wrote:
>
> Bonjour Daniel,
>
>> For csv, Fabien and Peter expressed the opinion that we shouldn't
>> create another fieldsep-like variable specifically for it, but instead
>> reuse fieldsep. That's what my latest patch does.
>>
>> Now it turns out that sharing fieldsep comes with some problems.
>
> Personnaly I do not have any problem with CSV defaulting to '|'
> separator, given that anyway people often use anything but a comma for
> the purpose, including '|'.
>
> However Pavel wants to block the patch on this point. Too bad.
>
> Maybe you can do (again) a patch with a 'fieldsep_csv' or whatever
> additional variable? Not sure about 'recordsep'...
>
> And then we forward to committers both version and they can chose
> whatever they think best, including not committing anything?
>
Would suggest the choice of 'fieldsep_csv' out of those two (a record
would correspond to the whole row), and the default being a comma.
Cheers,
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | legrand legrand | 2018-03-31 09:35:39 | Re: Planning counters in pg_stat_statements |
| Previous Message | Fabien COELHO | 2018-03-31 08:33:38 | Re: csv format for psql |