Horton

Re: plpgsql EXECUTE will not set FOUND

Kevin Grittner <kevin.grittner@wicourts.gov>

View thread View on postgr.es
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Robert Haas" <robertmhaas@gmail.com>, "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Dimitri Fontaine" <dfontaine@hi-media.com>, "PGDG" <pgsql-hackers@postgresql.org>
Date: 2009-10-23T15:07:18Z
Lists: 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