Re: proposal: plpgsql - Assert statement - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: proposal: plpgsql - Assert statement
Date
Msg-id CA+U5nMJi2q7kpXXg2iXXaD12N-m6YBLoUvzJhEEp5kprZyiLfQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: plpgsql - Assert statement  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: proposal: plpgsql - Assert statement  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: proposal: plpgsql - Assert statement  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 18 November 2014 01:00, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> On 11/17/14, 4:58 PM, Simon Riggs wrote:
>>>>
>>>> Great, looks good to me, marking as ready for committer.
>>
>>
>> What is wrong with using IF ?
>
>
> It's a hell of a lot wordier. I've previously created a more sophisticated
> "assert" framework to allow more control over things, but ended up also
> using it just for simple sanity checking because it was much nicer than
> typeing IF THEN RAISE ERROR END IF.

Why is that not a requirement for a less wordier form of IF?

IF (something) THEN action

Why is this problem specific to RAISE?


-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: inherit support for foreign tables
Next
From: Ashutosh Bapat
Date:
Subject: Re: postgres_fdw behaves oddly