Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id MAA94135
	for <pgsql-interfaces@postgreSQL.org>;
	Fri, 20 Aug 1999 12:36:48 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id MAA14996;
	Fri, 20 Aug 1999 12:33:52 -0400 (EDT)
To: StOo <stuart@comodo.net>
cc: interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] eekk tuples ok when there not! 
In-reply-to: Your message of Fri, 20 Aug 1999 15:20:58 +0000
	<37BD725A.23721DF1@comodo.net>
Date: Fri, 20 Aug 1999 12:33:52 -0400
Message-ID: <14994.935166832@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

StOo <stuart@comodo.net> writes:
> after calling PgConnection::Exec(const char *query);
> it returns PGRES_TUPLES_OK even when there is nothing in the table!

Yes.  Always has, always will.  PGRES_TUPLES_OK means you did a
SELECT and had no error --- it is not an error for the SELECT
to find no matching tuples.  You have to look at PQntuples
to find out how many tuples you got back.

			regards, tom lane