Re: PLPGSQL and FOUND stange behaviour after EXECUTE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Константин <beholder(at)mmska(dot)ru>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: PLPGSQL and FOUND stange behaviour after EXECUTE
Date: 2004-10-01 03:39:01
Message-ID: 4595.1096601941@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Neil Conway <neilc(at)samurai(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-10-01 03:46:52 Re: semicolon not required on END statement
Previous Message Neil Conway 2004-10-01 01:03:17 Re: PLPGSQL and FOUND stange behaviour after EXECUTE