Re: csv format for psql

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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: csv format for psql
Date: 2018-03-28 19:43:07
Message-ID: 2ec54f9b-5ace-6d84-589a-fc517c3f2752@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/28/2018 12:35 PM, David G. Johnston wrote:
> On Monday, March 26, 2018, Daniel Verite <daniel(at)manitou-mail(dot)org
> <mailto:daniel(at)manitou-mail(dot)org>> wrote:
>
>
> 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.
>
>
> I like to call it "Character Separated Values" now for just that reason.

Isn't the actual wording Character Delimited Values? I may be picking at
hairs here but every single time I use anything to import a CSV or other
delimited file (TAB or | usually) that is what the import screen says.

JD

>
> David J.

--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
*** A fault and talent of mine is to tell it exactly how it is. ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2018-03-28 20:01:40 Re: Using base backup exclusion filters to reduce data transferred with pg_rewind
Previous Message David Steele 2018-03-28 19:39:00 Re: Sample values for pg_stat_statements