Re: Updated COPY CSV patch

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Updated COPY CSV patch
Date: 2004-04-13 11:32:19
Message-ID: 2748.24.211.141.25.1081855939.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian said:
> Second, I found a problem with NULLs. If I do:
> .
> test=> create table test (x text, y text);
> CREATE TABLE
> test=> insert into test values ('', NULL);
> INSERT 17221 1
> test=>
>
> then this:
>
> test=> copy test to '/tmp/b' with csv;
>
> creates:
>
> "",
>
> and this:
>
> test=> copy test to '/tmp/b' with csv NULL 'fred';
>
> creates:
>
> ,fred
>
> Is that logical? A non-null field went from "" to nothing.
>

One more point about this - we can't force quoting of every non-null
value, which would remove the "inconsistency" you see here, because
spreadsheets especially infer information from whether or not a CSV value
is quoted. In particular, they will not usually treat a quoted numeric
value as numeric, which would be a very undesirable effect.

cheers

andrew

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruno Wolff III 2004-04-13 12:38:18 Re: Updated COPY CSV patch
Previous Message Andrew Dunstan 2004-04-13 10:58:24 Re: Updated COPY CSV patch