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 42C4952AA2 for ; Wed, 10 Aug 2005 07:26:59 -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 89301-07 for ; Wed, 10 Aug 2005 10:26:50 +0000 (GMT) Received: from ns.panforma.co.yu (ns.panforma.co.yu [212.200.122.36]) by svr1.postgresql.org (Postfix) with ESMTP id 44C5E52A11 for ; Wed, 10 Aug 2005 07:26:46 -0300 (ADT) Received: from [192.168.12.198] ([192.168.12.198]) by ns.panforma.co.yu (8.13.1/8.13.1) with ESMTP id j7AAQjTe017069 for ; Wed, 10 Aug 2005 12:26:47 +0200 Message-ID: <42F9D575.5010103@panforma.co.yu> Date: Wed, 10 Aug 2005 12:22:45 +0200 From: =?UTF-8?B?RHJhZ2FuIE1hdGnEhw==?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: PG 7.3.4 VS PG 8.0.3 Problem References: <1d219a6f05080910277cbf10b2@mail.gmail.com> <20050809183443.GA25232@winnie.fuhr.org> <1d219a6f050809120320cb1acb@mail.gmail.com> In-Reply-To: <1d219a6f050809120320cb1acb@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200508/128 X-Sequence-Number: 18447 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