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

From Kevin Grittner
Subject Re: plpgsql EXECUTE will not set FOUND
Date
Msg-id 4AE18056020000250002BE43@gw.wicourts.gov
Whole thread Raw
In response to Re: plpgsql EXECUTE will not set FOUND  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: plpgsql EXECUTE will not set FOUND
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Any change here is *not* a bug fix, it is a change of clearly
> documented and not-obviously-unreasonable behavior.  We have to take
> seriously the likelihood that it will break existing code.
Perhaps plpgsql could support tests of SQLSTATE, and recognize '02000'
(the standard value for "zero rows affected") to support the desired
new semantics?
-Kevin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: plpgsql EXECUTE will not set FOUND
Next
From: "Kevin Grittner"
Date:
Subject: Re: Using views for row-level access control is leaky