Re: COPY WITH CSV FORCE QUOTE *

From: Chris Spotts <rfusca(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY WITH CSV FORCE QUOTE *
Date: 2009-07-16 20:40:03
Message-ID: 4A5F9023.2030200@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus wrote:
> Andrew,
>
>> AFAICT on a brief look at the patch, it doesn't affect the quoting of
>> nulls on export, it just allows * as an alias for all columns for FORCE
>> QUOTE (as well as FORCE NOT NULL). But FORCE QUOTE has never forced
>> quoting of null values, only non-null values. We have never quoted null
>> values, and I'm fairly resistant to any suggestion that we should.
>
> See? That's what happens when I can't build the docs. ;-) (and
> there's no previous discussion of the feature).
>
>>
>> As for importing data from programs that produce all values in quotes
>> including null/missing values (your pro case above), arguably what we
>> need is another flag that would turn an empty string into a null.
>
> ooooh, TODO, please? There's a lot of this out there, and I've had to
> build sed into a lot of import routines.
>
+1 For that on the TODO, happens all the time...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2009-07-16 20:40:45 Re: WIP patch for TODO Item: Add prompt escape to display the client and server versions
Previous Message Merlin Moncure 2009-07-16 20:31:23 Re: Docbook toolchain interfering with patch review?