Dave Page wrote:
>
> > -----Original Message-----
> > From: Hiroshi Inoue [mailto:Inoue@tpf.co.jp]
> > Sent: 14 June 2001 11:09
> > To: Dave Page
> > Cc: Zoltan Kovacs; pgsql-odbc
> > Subject: Re: [ODBC] Error handling in ODBC
> >
> >
> > Dave Page wrote:
> > >
> >
> > [snip]
> >
> > >
> > > As far as I can tell, it is then not possible to access the notice
> > > from a client app (cetainly SQLError won't return it in my
> > test prog,
> > > yet I can quite happily get a real error from an invalid query for
> > > example.
> > >
> >
> > Hmm it may be possible that SQLERROR returns a notice message
> > in an appropriate condition(?????) though I'm not sure.
>
> Unfortunately I'm not really familiar enough with either C or the guts of
> the driver to know or be able to figure out in a reasonable amount of time
> (though I have spent hours staring at the code :-)) what exactly it is/is
> trying to do. I do know it's not doing what I need it to :-(, and - I
> suspect - what it should be doing (though these are not necessarily one and
> the same).
>
IMHO *ERROR* messages should return SQL_ERROR with the SQLSTATE <>
"00000". As for NOTICEs we seem to be able to change the driver to
return SQL_SUCCESS_WITH_INFO and let the succeeding SQLError() to
return the NOTICE message.
However I've not recognized the circumstances why both ERRORs and
(some) NOTICEs return SQL_ERROR with the SQLSTATE = '00000' now.
Comments ?
regards,
Hiroshi Inoue
