From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | "Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr>,"David Steele" <david(at)pgmasters(dot)net>,"PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: csv format for psql |
Date: | 2018-03-26 18:26:26 |
Message-ID: | ca824b41-7288-4f25-b2dc-daad8e022345@manitou-mail.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule wrote:
> b) the list of pset options is bloating - every possible new format can
> introduce fieldsep_X option
What new format?
The usefulness of fieldsep does not extend outside of xSV, and it's
no suprise that there have been no other use for a fieldsep-like
variable until now, with the other formats supported in psql.
In fact it's even absurd for any format to use a non-fixed separator
at a place that is key for being parsed unambiguously.
We could even support only the comma and make it non-configurable
based on the fact it's Comma-Separated-Values, not
Whatever-Separated-Values, except that won't do much
to serve the users interests, as the reality is that
people use various separators.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-03-26 18:31:36 | Re: Why does load_external_function() return PGFunction? |
Previous Message | Claudio Freire | 2018-03-26 17:47:23 | Re: [HACKERS] [PATCH] Vacuum: Update FSM more frequently |