From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: plpgsql - Assert statement |
Date: | 2014-11-18 20:27:19 |
Message-ID: | 546BABA7.9090102@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/18/2014 02:53 PM, Jim Nasby wrote:
> On 11/18/14, 9:31 AM, Andrew Dunstan wrote:
>>
>> Frankly, I find this whole proposal, and all the suggested
>> alternatives, somewhat ill-conceived. PLPGSQL is a wordy language. If
>> you want something more terse, use something else. Adding these sorts
>> of syntactic sugar warts onto the language doesn't seem like a
>> terribly good way to proceed.
>
> Such as?
>
> The enormous advantage of plpgsql is how easy it is to run SQL. Every
> other PL I've looked at makes that WAY harder. And that's assuming
> you're in an environment where you can install another PL.
>
> And honestly, I've never really found plpgsql to be terribly wordy
> except in a few cases ("assert" being one of them). My general
> experience has been that when I'm doing an IF (other than assert), I'm
> doing multiple things in the IF block, so it's really not that big a
> deal.
>
I frequently write one-statement bodies of IF statements. To me that's
not a big deal either :-)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Brightwell | 2014-11-18 20:30:04 | Re: Additional role attributes && superuser review |
Previous Message | Heikki Linnakangas | 2014-11-18 19:54:24 | Re: BRIN and PageIndexDeleteNoCompact |