Re: plpgsql EXECUTE will not set FOUND

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: plpgsql EXECUTE will not set FOUND
Дата
Msg-id b42b73150910230846v2d53143ag2595544077a5426e@mail.gmail.com
обсуждение исходный текст
Ответ на Re: plpgsql EXECUTE will not set FOUND  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers
On Fri, Oct 23, 2009 at 11:07 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> 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?

+1

I rarely use found because it's dangerous ...would be nice to have a
more rigorous test...

merlin


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: client_lc_messages
Следующее
От: Robert Haas
Дата:
Сообщение: Re: plpgsql EXECUTE will not set FOUND