> On 6 sep 2014, at 16:32, Marko Tiikkaja <ma...@joh.to> wrote: > > How do you run queries which affect more than one row in this mode? Because > that's crucial as well. We want something we can run 100% of our code on, > but with a slightly more convenient syntax than PL/PgSQL provides right when > coding defensively in the cases where exactly one row should be affected.
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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
