From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jim Martinez <jjm(at)bigbigorg(dot)org> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: false No rows returned error |
Date: | 2002-03-23 17:13:37 |
Message-ID: | 25863.1016903617@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Jim Martinez <jjm(at)bigbigorg(dot)org> writes:
> I am getting a No rows returned error from a php script when there are
> rows.
I don't think so ...
> // script dies here (line 36), falling to the exit clause.
> // A warning is printed also :
> // Warning: Supplied argument is not a valid
> // PostgreSQL result resource
I think that warning is what to pay attention to, and not the fact
that your script falls over when pg_numrows then chooses to return 0.
I don't know enough about PHP to know what you did wrong, but apparently
$res does not contain the kind of object pg_numrows expects. I think
it's a PHP problem, not an SQL issue at all.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Langille | 2002-03-23 17:35:14 | Re: false No rows returned error |
Previous Message | Jim Martinez | 2002-03-23 16:04:21 | false No rows returned error |