Re: NULL TIMESTAM problem

From: "Enrique Snchez" <sancheztru(at)hotmail(dot)com>
To: mike(at)fuhr(dot)org
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: NULL TIMESTAM problem
Date: 2006-03-09 19:55:35
Message-ID: BAY113-F30E5A0BB2EF9D6EA42249ED4EC0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


OK. the error was that: postgress didn't recognize which was the
NULLstring, because the format file was: value1*value2**value4, where the
delimiter is: * .

I learnd the default NULL string is '\N', but as you told me, you can
specify this in the command definition.

Thanks Michael.

>From: Michael Fuhr <mike(at)fuhr(dot)org>
>To: Enrique Snchez <sancheztru(at)hotmail(dot)com>
>CC: pgsql-general(at)postgresql(dot)org
>Subject: Re: [GENERAL] NULL TIMESTAM problem
>Date: Thu, 9 Mar 2006 12:26:10 -0700
>
>On Thu, Mar 09, 2006 at 12:49:14PM -0600, Enrique Snchez wrote:
> > I nedd to fill a database table x from a file With the COPY command an
>the
> > delimiter '*'.
> > This table has a timestamp null column (I declared like: ' birthday
> > timestamp NULL' ).
> >
> > But when I try to insert NULL values(specified in the file), postgres
>throw
> > an error.
>
>What's the error? How are the NULL values specified in the file?
>
> > I don't know how can I specify this NULL value wkthout an '\N'
>character.
>
>See the COPY documentation -- COPY has a NULL option that allows
>you to specify what string should be interpreted as NULL. Recent
>versions also have a CSV option that interprets empty strings as
>NULL.
>
>http://www.postgresql.org/docs/8.1/interactive/sql-copy.html
>
>(Use the documentation for whatever version you're running.)
>
>--
>Michael Fuhr
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Blaisdell 2006-03-09 19:58:15 Re: JDBC
Previous Message Bob Pawley 2006-03-09 19:50:38 JDBC