Re: PG 7.3.4 VS PG 8.0.3 Problem - Mailing list pgsql-admin

From Chris Hoover
Subject Re: PG 7.3.4 VS PG 8.0.3 Problem
Date
Msg-id 1d219a6f05081011331dc0bb76@mail.gmail.com
Whole thread Raw
In response to Re: PG 7.3.4 VS PG 8.0.3 Problem  (Dragan Matić <mlists@panforma.co.yu>)
Responses Re: [ODBC] PG 7.3.4 VS PG 8.0.3 Problem
List pgsql-admin
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ć <mlists@panforma.co.yu> 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
>

pgsql-admin by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: SQL Server 2000 to PostgreSQL 8.0.3
Next
From: "Magnus Hagander"
Date:
Subject: Re: Trouble Getting Database Server Started