Re: Handling NULL dates in "copy from" statement

From: Jason Earl <jason(dot)earl(at)simplot(dot)com>
To: "Tim Nelson" <nelsonx(at)earthlink(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Handling NULL dates in "copy from" statement
Date: 2001-12-10 17:48:31
Message-ID: 877krvc6fk.fsf@npa01zz001.simplot.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Try replacing the empty string with \N, that's what copy reads as
NULL.

Jason

"Tim Nelson" <nelsonx(at)earthlink(dot)com> writes:

> Is there a way to handle NULL date fields
> that I am trying to import from another database?
>
> ex:
>
> ...for a table with a single date field that allows NULL...
>
> echo "12/31/2000" | psql -c "copy date_tab from stdin using delimiters '|' "
> db_name
>
> ...works, but if I use a blank date...
>
> echo "" | psql -c "copy date_tab from stdin using delimiters '|' " db_name
>
> ...it fails with "Bad date external representation"...
>
> I've tried replacing the empty string with "NULL" and adding " with null as
> '' " to no avail.
>
> Any ideas? Thanks. Tim
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jason Earl 2001-12-10 17:52:41 Re: What is the practical limitation of no multi-threading?
Previous Message Lamar Owen 2001-12-10 17:41:44 Re: RedHat6.2 - postgres 7.1.2 lib confusion