Received: from gauss.deltav.hu (mail.deltav.hu [213.163.0.9]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5GFmja75018 for ; Sat, 16 Jun 2001 11:48:45 -0400 (EDT) (envelope-from ltibor@mail.tiszanet.hu) Received: from pcltibor ([213.163.10.100]) by gauss.deltav.hu (Netscape Messaging Server 3.6) with SMTP id AAA41BB; Sat, 16 Jun 2001 17:53:30 +0200 From: "Tibor Laszlo" To: "pgsql-odbc" Cc: =?iso-2022-jp?B?S292GyRCYUQbKEJzIFpvbHQbJEJhTxsoQg==?= Subject: RE: Error handling in ODBC Date: Sat, 16 Jun 2001 17:48:49 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Importance: Normal X-Archive-Number: 200106/45 X-Sequence-Number: 598 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@mail.tiszanet.hu