Re: csv format for psql

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: 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-07 10:00:59
Message-ID: CAFj8pRBX4nGA+ueR18pqwP3OGF85DTisY2aZshcy9jceTY8-5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2018-03-07 10:45 GMT+01:00 Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>:

>
> Hello Daniel,
>
> Attached is a v2 fixing the bugs you mentioned, and adding ---csv/-C
>> as discussed upthread. I'll add some regression tests shortly.
>>
>
> Basically I'm waiting for the version with regression tests before
> reviewing.
>
> It is unclear whether committer will like it.
>
> From my point of view being able to simply set postgres to generate csv is
> fine with me, with example uses such as:
>
> psql --csv 'TABLE Stuff;' > stuff.csv
>
> So that having the --csv option to turn to "full csv", i.e. set the format
> and various seperators as expected, would be a nice have.
>

There is commad -c and it should be used. The --csv options should not to
have a parameter. I don't like a idea to have more options for query
execution.

Regards

Pavel

>
> --
> Fabien.
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-03-07 10:10:34 Re: Some message fixes
Previous Message Tomas Vondra 2018-03-07 09:55:29 Re: [PROPOSAL] Shared Ispell dictionaries