> On 6 sep 2014, at 16:32, Marko Tiikkaja <marko@joh.to> 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