Re: plpgsql EXECUTE will not set FOUND - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plpgsql EXECUTE will not set FOUND
Date
Msg-id 9807.1256305954@sss.pgh.pa.us
Whole thread Raw
In response to Re: plpgsql EXECUTE will not set FOUND  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: plpgsql EXECUTE will not set FOUND
List pgsql-hackers
Dimitri Fontaine <dfontaine@hi-media.com> writes:
> I'll go search for more, meantime I'll just add the main goal of this
> new thread is to have -hackers know there is a real user demand for
> having EXECUTE set FOUND the same way it sets GET DIAGNOSTIC.

[shrug...]  There is also real user demand for not silently breaking
code that works now, which is what we risk anytime we change the set
of statements that can set FOUND.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: EvalPlanQual seems a tad broken
Next
From: Tom Lane
Date:
Subject: Re: Using views for row-level access control is leaky