| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: csv format for psql |
| Date: | 2018-03-09 07:40:40 |
| Message-ID: | alpine.DEB.2.20.1803090837390.31808@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> About "fieldsep_csv", I do not like much the principle of having
>>> different output variables to represent the same concept depending on
>>> the format. I would rather have reused fieldsep as in your previous
>>> submission and set it to "," when under --csv.
>>
>> yes
>>
>
> how will be possible to set different separator ';'? I don't see it with
> described design
Indeed, it should be possible. I think that the following should be made
to work:
psql --csv -P fieldsep=; -c 'TABLE foo' > foo.csv
So that it can be changed the semi-colon (or tab or whatever) style if
required.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-03-09 07:55:38 | Fixes for missing schema qualifications |
| Previous Message | Noah Misch | 2018-03-09 07:14:59 | Re: public schema default ACL |