Re: plpgsql EXECUTE will not set FOUND

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: plpgsql EXECUTE will not set FOUND
Дата
Msg-id 4AE18056020000250002BE43@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: plpgsql EXECUTE will not set FOUND  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: plpgsql EXECUTE will not set FOUND
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: plpgsql EXECUTE will not set FOUND
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Using views for row-level access control is leaky