X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CC97752936; Thu, 11 Aug 2005 16:36:45 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 13503-07; Thu, 11 Aug 2005 19:36:39 +0000 (GMT) Received: from fep02-app.kolumbus.fi (fep02-0.kolumbus.fi [193.229.0.44]) by svr1.postgresql.org (Postfix) with ESMTP id 1D6BE52E2E; Thu, 11 Aug 2005 16:36:33 -0300 (ADT) Received: from [192.168.1.101] (really [84.231.186.215]) by fep02-app.kolumbus.fi with ESMTP id <20050811193630.TEFP8199.fep02-app.kolumbus.fi@[192.168.1.101]>; Thu, 11 Aug 2005 22:36:30 +0300 Message-ID: <42FBA8BC.3040206@kolumbus.fi> Date: Thu, 11 Aug 2005 22:36:28 +0300 From: Marko Ristola User-Agent: Debian Thunderbird 1.0.2 (X11/20050331) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chris Hoover Cc: =?UTF-8?B?RHJhZ2FuIE1hdGnEhw==?= , pgsql-admin@postgresql.org, pgsql-odbc@postgresql.org Subject: Re: [ODBC] PG 7.3.4 VS PG 8.0.3 Problem References: <1d219a6f05080910277cbf10b2@mail.gmail.com> <20050809183443.GA25232@winnie.fuhr.org> <1d219a6f050809120320cb1acb@mail.gmail.com> <42F9D575.5010103@panforma.co.yu> <1d219a6f05081011331dc0bb76@mail.gmail.com> In-Reply-To: <1d219a6f05081011331dc0bb76@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.102 tagged_above=0 required=5 tests=[AWL=0.052, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200508/147 X-Sequence-Number: 18466 Hello. I have some bad experience with RHEL 2 and PostgreSQL ODBC. I have seen there a following problem: An ODBC application gets SUCCESS regardless of wether the SQL command succeeded or not! I don't know, wether the psqlodbc behaviour was caused by application's ODBC calling convention, or is there something fatally wrong. I do remember, that psql command line tool worked. Isql (ODBC command line tool for UnixODBC) did not notice errors either (please check, if you need this information). So it seemed, that the RHEL2's psqlodbc is bad, and nobody uses it. The problem is solveable by replacing the psqlodbc driver with a working one. Regards, Marko Ristola Chris Hoover wrote: >Ok, I think I have narrowed this down even further. I went and >installed a 7.3.4 db on our RHEL 4 server and is exibiting the same >behavior. I believe there is something with RHEL 2.1 and PostgreSQL >that causes the wrong sqlcode to be returned. That is the only thing >I can figure out. > >I'm not sure where to go from here. Any ideas? > >Chris > >On 8/10/05, Dragan Matić wrote: > > >>Chris Hoover wrote: >> >> >> >>>Sorry, I should have given some setup details. >>> >>> >>>When this query is run against either version of PG, it does not >>>return any rows (obviously due to the issue with hdr_create_dt). I >>>actually walked through the code using our cobol debugger to find this >>>issue. When it checks the sqlca.sqlcode record returned by this query >>>in 7.3.4, it has a 0. In 8.0.3, it has a 100. >>> >>> >>> >>> >>> >>We are also using Cobol (Micro Focus NetExpress) and we haven't noticed >>any changes when moving from version 7.x to version 8. >>Another question is whether sqlcode was returning good result until now? >>As far as I know (and it works that way with us) sqlcode _should_ have a >>value of 100 when query returns no rows. Value of 0 indicates there were >>no errors, and value of 100 means 'no rows found'. >> >>With Regards >> >>Dragan Matic >> >> >> >>---------------------------(end of broadcast)--------------------------- >>TIP 1: 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 >> >> >> > >---------------------------(end of broadcast)--------------------------- >TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > >