Re: PL/pgSQL 2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Tiikkaja <marko(at)joh(dot)to>
Cc: Joel Jacobson <joel(at)trustly(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/pgSQL 2
Date: 2014-09-02 14:21:50
Message-ID: 3730.1409667710@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marko Tiikkaja <marko(at)joh(dot)to> writes:
> For example:

> UPDATE foo WHERE bar = 1; -- must affect exactly one row
> PERFORM UPDATE foo WHERE bar = 1; -- can affect any number of rows

FWIW, I agree with the position that this would be a completely wrong
thing to do. UPDATE should work like it does in plain SQL. If you want
a restriction to "exactly one row", that needs to be a modifier.

I take no position on how the modifier should be spelled, though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2014-09-02 14:23:21 Re: ALTER SYSTEM RESET?
Previous Message Joel Jacobson 2014-09-02 14:15:40 Re: PL/pgSQL 2