Re: PL/PgSQL STRICT

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PL/PgSQL STRICT
Date: 2013-02-26 22:34:24
Message-ID: 512D3870.5060007@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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.)

I agree with other commentators that it would be useful, but that the
word STRICT should be near the word INTO, making it clear that the
STRICTness is tied to the variable assignment.

I do think we can deal with the "more than one" case once PL/pgSQL INTO
actually supports assigning more than one row to a variable, which
currently it doesn't. At that time, we'll just have to remember to
update the code for STRICT as well.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2013-02-26 22:51:52 Re: initdb ignoring options?
Previous Message Greg Smith 2013-02-26 22:16:34 initdb ignoring options?