| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | Rajat Katyal <rajatk(at)intelesoftech(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PERFORM statement inside procedure |
| Date: | 2004-04-06 20:44:22 |
| Message-ID: | 1504.1081284262@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bill Moran <wmoran(at)potentialtech(dot)com> writes:
> Rajat Katyal wrote:
>> But FOUND variable is always returning true even my query is
>> returning *0 records.*
> FOUND appears to work correctly in the hundreds of stored procedures I wrote
> last month. (At least, I haven't found any problems _yet_)
Works for me too, in recent releases. I believe PERFORM did not originally
set FOUND ... are you reading the documentation that goes with your server
version?
[ digs in CVS logs... ] Here we go:
2002-06-24 19:12 tgl
* src/pl/plpgsql/src/pl_exec.c: plpgsql's PERFORM statement now
sets FOUND depending on whether any rows were returned by the
performed query. Per recent pgsql-general discussion.
So it should work in 7.3 or later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-06 20:55:58 | Re: Cursors and Transactions, why? |
| Previous Message | Frank Finner | 2004-04-06 20:26:42 | Re: Whats missing from postgresql |