Re: PL/pgSQL 2

From: Joel Jacobson <joel(at)trustly(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 13:32:47
Message-ID: CAASwCXct9c5=39KoBS3YR7kqWrOeritGzBCvdiWqkN+xkJVGJw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 2, 2014 at 2:29 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> In the mailing list thread that you linked there, Tom suggested using
> "STRICT UPDATE ..." to mean that updating 0 or >1 rows is an error
> (http://www.postgresql.org/message-id/16397.1356106923@sss.pgh.pa.us) What
> happened to that proposal?

From the STRICT mail thread, this was the last post:

>"Marko Tiikkaja" <marko(at)joh(dot)to> writes:
>> If I'm counting correctly, we have four votes for this patch and two votes
>> against it.
>> Any other opinions?
>
>FWIW, I share Peter's poor opinion of this syntax. I can see the
>appeal of not having to write an explicit check of the rowcount
>afterwards, but that appeal is greatly weakened by the strange syntax.
>(IOW, if you were counting me as a + vote, that was only a vote for
>the concept --- on reflection I don't much like this implementation.)
>regards, tom lane

I think it's much better to make it the default behaviour in plpgsql2
than to add a new syntax to plpgsql,
because then we don't have to argue what to call the keyword or where to put it.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomonari Katsumata 2014-09-02 13:35:11 Re: proposal: rounding up time value less than its unit.
Previous Message Arthur Silva 2014-09-02 13:30:11 Re: [REVIEW] Re: Compression of full-page-writes