Re: proposal: plpgsql - Assert statement

From: Petr Jelinek <petr(at)2ndquadrant(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: plpgsql - Assert statement
Date: 2014-11-18 21:19:40
Message-ID: 546BB7EC.7000805@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18/11/14 22:11, Pavel Stehule wrote:
>
> 2014-11-18 21:27 GMT+01:00 Andrew Dunstan <andrew(at)dunslane(dot)net
> <mailto:andrew(at)dunslane(dot)net>>:
>
>
> I frequently write one-statement bodies of IF statements. To me
> that's not a big deal either :-)
>
>
> anybody did it, but it doesn't need so it is perfect :) I understand
> well to Jim' feeling.
>
> I am looking to Ada 2005 language ... a design of RAISE WITH shows so
> RAISE statement is extensible in Ada too. Sure - we can live without it,
> but I don't think so we do some wrong with introduction RAISE WHEN and I
> am sure, so a live with this feature can be more fun for someone, who
> intensive use this pattern.
>

Personally, I see this as natural extension of the conditional block
control which we already have for loops with CONTINUE WHEN and EXIT
WHEN. This basically extends it to any block and it seems quite natural
to have it for me...

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-11-18 21:23:15 Re: Review of Refactoring code for sync node detection
Previous Message Pavel Stehule 2014-11-18 21:11:48 Re: proposal: plpgsql - Assert statement