Re: plpgsql defensive mode

Поиск
Список
Период
Сортировка
Искать
От
Joel Jacobson
Тема
Re: plpgsql defensive mode
Дата
Msg-id
-84707453404872238@unknownmsgid
Ответ на
Список
Дерево обсуждения
plpgsql defensive mode Pavel Stehule <pavel.stehule@gmail.com>
Re: plpgsql defensive mode Marko Tiikkaja <marko@joh.to>
Re: plpgsql defensive mode Joel Jacobson <joel@trustly.com>
Re: plpgsql defensive mode Joel Jacobson <joel@trustly.com>
Re: plpgsql defensive mode Marko Tiikkaja <marko@joh.to>
Re: plpgsql defensive mode Pavel Stehule <pavel.stehule@gmail.com>
Re: plpgsql defensive mode Marko Tiikkaja <marko@joh.to>
Re: plpgsql defensive mode Pavel Stehule <pavel.stehule@gmail.com>
Improving PL/PgSQL (was: Re: plpgsql defensive mode) Marko Tiikkaja <marko@joh.to>
Re: Improving PL/PgSQL Jan Wieck <jan@wi3ck.info>
Re: Improving PL/PgSQL (was: Re: plpgsql defensive mode) Pavel Stehule <pavel.stehule@gmail.com>
Re: Improving PL/PgSQL Marko Tiikkaja <marko@joh.to>
Re: Improving PL/PgSQL (was: Re: plpgsql defensive mode) Pavel Stehule <pavel.stehule@gmail.com>
Re: plpgsql defensive mode Joel Jacobson <joel@trustly.com>
> On 6 sep 2014, at 16:32, Marko Tiikkaja  wrote:
>
> How do you run queries which affect more than one row in this mode? Becau=
se that's crucial as well.  We want something we can run 100% of our code o=
n, but with a slightly more convenient syntax than PL/PgSQL provides right =
when coding defensively in the cases where exactly one row should be affect=
ed.

If we would have ORDER BY also for UPDATE/DELETE then one could just
order by something arbitrary to express multiple or zero rows are OK,
even if not being interested in the order.

>
>
> .marko
В списке pgsql-hackers по дате отправления
От: Marko Tiikkaja
Дата:
Сообщение: Re: plpgsql defensive mode
От: Bruce Momjian
Дата:
FAQ