| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:46:37 |
| Message-ID: | b42b73150910230846v2d53143ag2595544077a5426e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 23, 2009 at 11:07 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> 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?
+1
I rarely use found because it's dangerous ...would be nice to have a
more rigorous test...
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-10-23 15:50:24 | Re: plpgsql EXECUTE will not set FOUND |
| Previous Message | Alvaro Herrera | 2009-10-23 15:28:23 | Re: client_lc_messages |