Re: csv format for psql - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: csv format for psql
Date
Msg-id 2ec54f9b-5ace-6d84-589a-fc517c3f2752@commandprompt.com
Whole thread Raw
In response to Re: csv format for psql  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: csv format for psql  (Isaac Morland <isaac.morland@gmail.com>)
List pgsql-hackers
On 03/28/2018 12:35 PM, David G. Johnston wrote:
On Monday, March 26, 2018, Daniel Verite <daniel@manitou-mail.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.   *****

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Sample values for pg_stat_statements
Next
From: Fujii Masao
Date:
Subject: Re: Using base backup exclusion filters to reduce data transferredwith pg_rewind