Re: csv format for psql
| От | Daniel Verite |
|---|---|
| Тема | Re: csv format for psql |
| Дата | |
| Msg-id | 26659c9d-da8a-49e2-954b-b0f8d7729813@manitou-mail.org обсуждение исходный текст |
| Ответ на | Re: csv format for psql (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: csv format for psql
|
| Список | pgsql-hackers |
Michael Paquier wrote:
> -C could also be useful for other things, say compression.
The patch does not grab any short letter, as the consensus
went that way.
> + pset.popt.topt.fieldSepCsv = pg_strdup(",");
> Let's store that in a variable instead of hardcoding it.
I guess it could go into a #define in psql/settings.h, along with
these:
#define DEFAULT_FIELD_SEP "|"
#define DEFAULT_RECORD_SEP "\n"
> In the regression tests, "col 9" is wanted with a newline?
Yes, since we support column names with embedded newlines (even
though it's hard to think of a legit use case for that) and CSV fields
support embedded newlines too.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
В списке pgsql-hackers по дате отправления: