Re: plpgsql EXECUTE will not set FOUND

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dimitri Fontaine" <dfontaine(at)hi-media(dot)com>, "PGDG" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql EXECUTE will not set FOUND
Date: 2009-10-23 15:07:18
Message-ID: 4AE18056020000250002BE43@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-10-23 15:15:05 Re: Using views for row-level access control is leaky
Previous Message Tom Lane 2009-10-23 14:50:33 Re: plpgsql EXECUTE will not set FOUND