Re: csv format for psql
| От | Pavel Stehule |
|---|---|
| Тема | Re: csv format for psql |
| Дата | |
| Msg-id | CAFj8pRCip9+ARiKrM6H97FfT_JtP9-S2Yu70bixba8bcBN1VzA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: csv format for psql ("Daniel Verite" <daniel@manitou-mail.org>) |
| Список | pgsql-hackers |
2018-04-07 13:55 GMT+02:00 Daniel Verite <daniel@manitou-mail.org>:
Pavel Stehule wrote:
> so we can to have
>
> \pset format xxx
>
> and set of local possibly changed defaults
>
> \pset csv_fieldsep ,
> \pset csv_tuplesonly on
> \pset unaligned_fieldsep |
> \pset unaligned_tuplesonly off
tuples_only (\t) is a single setting that is currently used by all
formats. It makes sense as it is and I don't quite see what we
would gain by "exploding" it.
It was a example, how the one default can be not good enough.
Usually we expect in align, unalign headers by default. But somebody can expect tuples only by default for CSV format.
There's also "footer" that goes in tandem with "tuples_only",
to switch off the footer while keeping the header and title.
Whatever change is considered to "tuples_only", "footer" must
be considered with it.
For the csv format, tuples_only=off is interpreted as "output the header"
and tuples_only=on as "don't output the header". This is consistent
with what other formats do.
My note was not about the implementations, it was about different expectations of some users - looks on Isaac's mail, pls.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
В списке pgsql-hackers по дате отправления: