Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
Date
Msg-id 11620.1284646377@sss.pgh.pa.us
Whole thread Raw
In response to "EXECUTE ... into var" doesn't set FOUND: bug or feature?  (Louis-David Mitterrand <vindex+lists-pgsql-general@apartia.org>)
Responses Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
List pgsql-general
Tree view 
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.

            regards, tom lane

pgsql-general by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: value
Next
From: Louis-David Mitterrand
Date:
Subject: Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?