| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal - support tsv output format for psql |
| Date: | 2020-12-23 15:54:17 |
| Message-ID: | 20201223155417.GH9170@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 23, 2020 at 04:39:48PM +0100, Pavel Stehule wrote:
>
>
> st 23. 12. 2020 v 16:24 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
>
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Wed, Dec 23, 2020 at 07:18:24AM +0100, Pavel Stehule wrote:
> >> Implementation of tsv format should not be hard.
> >> What do you think about this?
>
> > How would you handle tabs in the data?
>
> The main problem with csv is the severe lack of standardization
> around what to do with corner cases (delimiters in data, empty
> fields, etc). Seems like "tsv" would be even worse. Is there
> an actual standard anywhere?
>
>
> Probably not - there are just common conventions.
>
> standard disallows tab chars inside
>
> https://www.iana.org/assignments/media-types/text/tab-separated-values
Is it too awkward to throw an error if there is a tab?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2020-12-23 16:07:55 | Re: proposal - support tsv output format for psql |
| Previous Message | Pavel Stehule | 2020-12-23 15:39:48 | Re: proposal - support tsv output format for psql |