RE: Error handling in ODBC

Hiroshi Inoue writes:

> Recently I found the case that NOTICE causes an error in ODBC
> while examining Kristis' error report.
>
> It seems that NOTICE had never been the cause of SQL_ERROR
> before Zoltan's change about a year ago. Before his change *NOTICE*
> only caused a PGRES_NONFATAL_ERROR and SC_execute()
> returned SQL_SUCCESS_WITH_INFO. However currently *ERROR*
> also causes a PGRES_NONFATAL_ERROR and SC_Execute()
> returns SQL_ERROR.
> Why was this changed ?

Zoltan changed the driver because nobody else did it. As I recall, we asked this
list to correct the driver to work correctly with 7.0 pre releases with RI, but
we received no answers. We tried to correct the problem for ouselves. It worked.
But later we were asked to share the patch. Lastly it used to commit the main
CVS by sombody else but we asked this list again to werify the modifycatons by
sombody knowing something about ODBC and the current driver.

> I'd like to put it back if there's no reason.

I think it should be corrected. But if I rmember correctly, the patch was for
report RI violatoions to the app, and these errors comes as NOTICEs not ERRORs.
May I wrong? Is it the case now?

We still use the old patched driver. (It says "(non fatal)" error this case in
the error message - may the shared patch says it too.)

In addition later we encountered the same problem as you... And Zoltan made his
second patch, against the backend to do not drop other NOTICE-s :-) And it works
fine too... :-)) Is somebody interested in? :-)))

Regards,

Tibor Laszlo
ltibor(at)mail(dot)tiszanet(dot)hu