Re:

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: zoop(at)lone(dot)ath(dot)cx
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re:
Date: 2003-08-21 02:48:13
Message-ID: 20030821024813.GC24904@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Aug 20, 2003 at 20:59:43 -0000,
zoop(at)lone(dot)ath(dot)cx wrote:
> I upgraded to 7.3.3 from 7.2 something. I guess the insert statment no longer
> accepts a zero lenght string like ''
> ERROR: pg_atoi: zero-length string
>
> Is there a way to make this work so it will put Null in the place of it?

Note that previously empty strings were treated as zero, not null (unlike
when using Oracle) when used for numeric values.

It is hard to give you concrete advice without knowing more about how
the data is collected. But having the application emit NULL or '0' (depending
on which you want) instead of '' is probably the way you want to go (if you
can). If you are using COPY, then there is a way to say that the empty
string represents a NULL.

In response to

  • at 2003-08-20 20:59:43 from zoop

Browse pgsql-general by date

  From Date Subject
Next Message Philip Boonzaaier 2003-08-21 02:49:39 Re: Bulk Insert / Update / Delete
Previous Message expect 2003-08-21 02:29:16 Re: 7.4b1 vs 7.3.4 performance