Re: PLPGSQL and FOUND stange behaviour after EXECUTE - Mailing list pgsql-bugs

From Tom Lane
Subject Re: PLPGSQL and FOUND stange behaviour after EXECUTE
Date
Msg-id 4595.1096601941@sss.pgh.pa.us
Whole thread Raw
In response to Re: PLPGSQL and FOUND stange behaviour after EXECUTE  (Neil Conway <neilc@samurai.com>)
Responses Re: PLPGSQL and FOUND stange behaviour after EXECUTE
List pgsql-bugs
Neil Conway <neilc@samurai.com> writes:
> On Fri, 2004-10-01 at 02:26, Tom Lane wrote:
>> EXECUTE does not set the FOUND flag.

> Is there a good reason for this behavior?

Possibly not.  Can EXECUTE determine how the executed statement would
have set the flag?  Should we assume that the function doing the EXECUTE
knows exactly what it's executing and what the implications on FOUND
ought to be?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Neil Conway
Date:
Subject: Re: PLPGSQL and FOUND stange behaviour after EXECUTE
Next
From: Tom Lane
Date:
Subject: Re: semicolon not required on END statement