| From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: improve FOUND in PL/PgSQL |
| Date: | 2002-08-15 02:20:50 |
| Message-ID: | 878z386ewt.fsf@klamath.dyndns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> BTW, the text still fails to make it clear that the statements will in
> fact reset FOUND to false when they process zero rows (or whatever).
> One could easily read this text as saying that FOUND will be the logical
> OR of whether all the statements-so-far found a row.
>
> It might also be good to spell out that FOUND is local in each plpgsql
> function, not a global variable.
Ok, a revised patch is attached. Thanks for the feedback.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| Attachment | Content-Type | Size |
|---|---|---|
| plpgsql_found-6.patch | text/x-patch | 20.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-08-15 02:33:35 | Re: improve SET CONSTRAINTS |
| Previous Message | Tom Lane | 2002-08-14 23:35:56 | Re: improve FOUND in PL/PgSQL |