2007/10/16, Neil Conway <[EMAIL PROTECTED]>:
> On Tue, 2007-10-16 at 11:24 +1000, Brendan Jurd wrote:
> > Is there a technical reason we do not set the value of FOUND when
> > executing a dynamic statement in plpgsql?
>
> See prior discussion:
>
> http://archives.postgresql.org/pgsql-bugs/2004-
On 10/16/07, Neil Conway <[EMAIL PROTECTED]> wrote:
> See prior discussion:
>
> http://archives.postgresql.org/pgsql-bugs/2004-10/msg1.php
Thanks for the link. I did search the archives but unfortunately
terms like 'found' and 'execute' generate a lot of unwanted matches =)
>
> It would
On Tue, 2007-10-16 at 11:24 +1000, Brendan Jurd wrote:
> Is there a technical reason we do not set the value of FOUND when
> executing a dynamic statement in plpgsql?
See prior discussion:
http://archives.postgresql.org/pgsql-bugs/2004-10/msg1.php
It would be easy enough to have EXECUTE
Hi hackers,
Is there a technical reason we do not set the value of FOUND when
executing a dynamic statement in plpgsql?
It seems surprising that FOUND is set by SELECT, PERFORM, UPDATE,
INSERT, DELETE, etc, *except* when those statements are invoked by
EXECUTE.
I had a brief look at the code in
