BUG #5268: PQgetvalue incorrectly returns 0

From: "Mike Landis" <mlandis(at)pnmx(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5268: PQgetvalue incorrectly returns 0
Date: 2010-01-07 04:11:03
Message-ID: 201001070411.o074B3Gu070528@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5268
Logged by: Mike Landis
Email address: mlandis(at)pnmx(dot)com
PostgreSQL version: 8.4.1
Operating system: Vista
Description: PQgetvalue incorrectly returns 0
Details:

When I execute the following SQL:

"SELECT COUNT(*) FROM information_schema.tables WHERE table_name='proxies'"

in the PGAdmmin 1.10.0, rev 7945-7946 query tool, I get "1" (the correct
answer). When I run the exact same SQL in a C program, I get a result set
with one tuple and one field (so far so good), but when I run
PQgetvalue(resultSet,0,0) I get "0" (wrong answer).

Am I missing something? You can't do squat in a client program without
PQgetvalue(). Is any sort of regression test being run against libpq
functions?

What can I do to get this resolved?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mike Landis 2010-01-07 04:13:11 email addresses
Previous Message Tom Lane 2010-01-06 16:03:56 Re: BUG #5267: initdb fails on AIX: could not identify current directory