Re: COPY command WITH NULLs bug?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "P(dot) Dwayne Miller" <dmiller(at)espgroup(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY command WITH NULLs bug?
Date: 2001-09-11 16:22:10
Message-ID: 2563.1000225330@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"P. Dwayne Miller" <dmiller(at)espgroup(dot)net> writes:
> It appears, and I could easily be mistaken, that the COPY command does
> not allow NULLs into a timestamp field, even though the field is defined
> to accept nulls.

Not sure what your problem is, but that's not it. Perhaps you've got a
problem with stray carriage returns (\r\n instead of \n), or what you
have in the file isn't actually equal to what you specified as the WITH
NULL string, or something else.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2001-09-11 16:38:11 Re: Beta timing
Previous Message Thomas Lockhart 2001-09-11 16:14:03 Re: factorial doc bug?