Re: postgres error reporting

New in 7.3, you can specify an empty COPY column for an integer.  It has
to be a zero or some other value.

---------------------------------------------------------------------------

Chisel Wright wrote:
> I like postgres, I find I get on much better with it than mysql.
> I have one really big problem with it though.
>
> Why is the error reporting so bad/vague for failed inserts?
>
> I have a perl script that's doing an insert query with 45-50 fields.
> There seems to be some bad data in the file I'm importing from.
>
> The message from postgres:
>
>   DBD::Pg::db do failed: ERROR:  pg_atoi: zero-length string at
> /path/to/Module.pm line 348, <STDIN> line 1.
>
> Which field doesn't it like?! Why can't it say something like:
>
>   DBD::Pg::db do failed: ERROR:  pg_atoi: zero-length string in field
> SomeTableField ....
>
> Is there something I'm missing that will give me this information?
>
> It's nothing to do with the perl either. Pasting the query into psql
> gives:
>
>   ERROR:  pg_atoi: zero-length string
>
> No clues as to which field or piece of data it is complaining about.
>
> Does anyone know how to find this out?
>
>
> Chisel
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

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