Re: postgres error reporting

The problem is that the error comes at a very low level in the code.

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

Mike Mascari wrote:
> From: "Bruce Momjian" <pgman@candle.pha.pa.us>
> >
> > New in 7.3, you can specify an empty COPY column for an
> integer.  It has
> > to be a zero or some other value.
>
> That's true of course (that you cannot specify an empty column
> for an integer). But Chisel's complaint still remains; the error
> reporting in some messages (particularly type-related errors)
> fails to provide any concrete information as to which attribute
> of which table caused the failure. One would have to log queries
> to determine where the failure took place. I don't think its
> unfair to say that other DBMS products do a better job of
> reporting more details of the failure - schema, table,
> attribute, etc.
>
> Mike Mascari
> mascarm@mascari.com
>
> >
> > 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?
> > >
> > >   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?
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>

--
  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