Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature? - Mailing list pgsql-general

From Louis-David Mitterrand
Subject Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
Date
Msg-id 20100916141524.GA12956@apartia.fr
Whole thread Raw
In response to Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
On Thu, Sep 16, 2010 at 10:12:57AM -0400, Tom Lane wrote:
> Louis-David Mitterrand <vindex+lists-pgsql-general@apartia.org> writes:
> > I noticed that in a pl/pgsql function FOUND is not set after an
> >     EXECUTE ... into var;
> > Bug or feature?
>
> It's behaving as documented:
> http://www.postgresql.org/docs/9.0/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-DIAGNOSTICS
>
> Adding EXECUTE to the list of statements that change FOUND would have a
> rather large risk of breaking existing plpgsql functions, IMO.

but is really surprising and non-intuitive, given that 'return query
execute' does.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
Next
From: Pavel Stehule
Date:
Subject: Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?