Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?

From: Louis-David Mitterrand <vindex+lists-pgsql-general(at)apartia(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
Date: 2010-09-16 14:15:24
Message-ID: 20100916141524.GA12956@apartia.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 16, 2010 at 10:12:57AM -0400, Tom Lane wrote:
> Louis-David Mitterrand <vindex+lists-pgsql-general(at)apartia(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2010-09-16 14:23:09 Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
Previous Message Tom Lane 2010-09-16 14:12:57 Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?