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 A9E5B52A25 for ; Tue, 9 Aug 2005 17:18:05 -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 82765-02 for ; Tue, 9 Aug 2005 20:18:04 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by svr1.postgresql.org (Postfix) with ESMTP id 74B2E52C6D for ; Tue, 9 Aug 2005 17:18:02 -0300 (ADT) Received: by zproxy.gmail.com with SMTP id o37so220085nzf for ; Tue, 09 Aug 2005 13:18:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tDAxL6//dtLIUytsjHVYVcL2Vw30C+wsy8ZQzwR85LAXuYrWhQIVmZvK6da0UQkyvT8ugV5t9mmOdXtlAXC+6jjr0dThqO5u/T+e65mPpLuoNNqKF6pMWb6bhcfKbcohLuWieyD5YIqg4nyGRnl63TLFVA9l3SpzCU1Sp2qkLZU= Received: by 10.36.8.6 with SMTP id 6mr1326218nzh; Tue, 09 Aug 2005 13:18:04 -0700 (PDT) Received: by 10.36.24.2 with HTTP; Tue, 9 Aug 2005 13:18:03 -0700 (PDT) Message-ID: <1d219a6f05080913185bba2683@mail.gmail.com> Date: Tue, 9 Aug 2005 16:18:04 -0400 From: Chris Hoover To: Tom Lane , pgsql-odbc@postgresql.org Subject: Re: PG 7.3.4 VS PG 8.0.3 Problem Cc: Michael Fuhr , pgsql-admin@postgresql.org In-Reply-To: <18535.1123617605@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1d219a6f05080910277cbf10b2@mail.gmail.com> <20050809183443.GA25232@winnie.fuhr.org> <1d219a6f050809120320cb1acb@mail.gmail.com> <18535.1123617605@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200508/120 X-Sequence-Number: 18439 Tom, I'll send this over to the odbc list. However, the odbc driver is liked into our cobol environment. I did not change the driver. We are running the 7.2.5 odbc driver. This is why I am pointing to a difference in the db responses. The entire environment is the exactly same except for the database versions (I am actually running the exact same code and odbc driver against the 2 db's). I can have the application connect via odbc to my 7.3.4 instance and get the sqlcode of 0. I can have the same application with the same odbc connect via odbc to my 8.0.3 instance and I get the sqlcode of 100. This is what is pointing me to a problem with one of the db's. It appears that the sqlca code has had to of changed between the 7.3.4 and 8 code and is now behaving in a different (and unexpected) manner. BTW, which version is correct? Should a no rows return query give a 0 or a= 100? Chris On 8/9/05, Tom Lane wrote: > Chris Hoover writes: > > Anyway, I'm not sure how to give you a simple example. We are running > > a cobol application that is connecting to PostgreSQL via odbc. The > > application runs on one linux box and the database on a seperate one. >=20 > Hmm. I seriously doubt that the server's response to the query has > changed any. What seems more likely is that the ODBC driver has changed > its behavior. Can you try linking your app with the older ODBC driver > and running it against the newer server? >=20 > Also, pgsql-odbc is probably a better place to ask about it. >=20 > regards, tom lane >