| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| 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 16:48:00 |
| Message-ID: | CAFj8pRAEnsvExWR+yfzPQdCa3HcjiaR9ppO3UDOwuOgXXDkvJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2018-03-09 8:40 GMT+01:00 Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>:
>
> 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.
>
ok, then all is ok
Regards
Pavel
>
> --
> Fabien.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emre Hasegeli | 2018-03-09 17:05:32 | Re: Precision loss casting float to numeric |
| Previous Message | Peter Eisentraut | 2018-03-09 16:07:55 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |