Re: COPY for CSV documentation

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: COPY for CSV documentation
Date: 2004-04-12 15:46:30
Message-ID: 200404121546.i3CFkU502820@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Andrew Dunstan wrote:
> In fact, in the patch I sent in, no quoted string is marked as null when
> being read (so even if you use \N as the null marker, "\N" will be that
> literal and not a null marker). And the null marker, whatever it is,
> should be made quote safe by us throwing an error if it contains the
> quote marker, just as we now make sure that the null marker is
> delimiter-safe.

What value does an int column get if the input file has ',,'. Don't
tell me zero? :-) Error?

> I will check on the write behaviour - it might need ammending too.
>
> I'll submit a revised patch based on the original syntax scheme, and
> then you (Bruce) can make the syntax/psql changes that seem to be agreed
> on now - is that ok?

OK, go as far as you want and post it. I will turn around a new patch
in a few hours after you post.

> The default NULL value issue can be determined at the end of any
> exhaustive debate we have - in the end it's a one line code change ;-)

Agreed.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-04-12 15:59:34 change for stdin/stdout for \copy
Previous Message Fabien COELHO 2004-04-12 15:36:55 aclitem accessor functions