From: | Marko Tiikkaja <marko(at)joh(dot)to> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: plpgsql - Assert statement |
Date: | 2014-09-09 07:49:48 |
Message-ID: | 540EB11C.2060603@joh.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2014-09-09 07:54, Craig Ringer wrote:
> On 09/05/2014 05:21 PM, Pavel Stehule wrote:
>>
>> *shrug* Doing it in SQL would probably break more stuff. I'm trying to
>> contain the damage. And arguably, this is mostly only useful in PL/PgSQL.
>
> I've wanted assertions in SQL enough that I often write trivial wrappers
> around `raise` in PL/PgSQL for use in `CASE` statements etc.
Yeah, as have I. I've also advocated that there should be a
raise_exception(text, anyelement) anyelement function shipped with
postgres.
But this is something different; this is just a single statement which
asserts that some expression evaluates to true. Even if we allowed it
to be used as a scalar expression, there's still the problem anyelement
is commonly used to work around.
.marko
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-09-09 08:54:26 | Re: pgcrypto: PGP armor headers |
Previous Message | Heikki Linnakangas | 2014-09-09 07:01:31 | Re: Stating the significance of Lehman & Yao in the nbtree README |