From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Brendan Jurd" <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Syntax decisions for pl/pgsql RAISE extension |
Date: | 2008-05-12 18:40:46 |
Message-ID: | 162867790805121140ocb578cm8460181bf84b7e5e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2008/5/12 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
>> 2008/5/12 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>>> It would get less annoying if we allowed user-declared exception names.
>
>> Tom, it's exactly like my patch that you rejected two years ago.
>
> Uh, no, not "exactly like" --- that patch doesn't have anything to do
> with the SQL/PSM syntax, and not much with the SQL/PSM semantics.
> As I read the spec, a condition name isn't a variable and so you can't
> do runtime assignment to it (and unlike Neil, I don't think you should
> be able to do so).
>
In plpgsql I prefer PL/SQL syntax. Mix SQL/PSM and PL/SQL will be
mismas. But I like idea, so you can set dynamically SQLSTATE and other
params - because you can write own wrapper for RAISE statement. It's
can be usable for centralized exception management. I can do it in C,
but there are lot of users, that could use only plpgsql.
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-05-12 18:43:59 | Re: Syntax decisions for pl/pgsql RAISE extension |
Previous Message | Pavel Stehule | 2008-05-12 18:35:44 | Re: Syntax decisions for pl/pgsql RAISE extension |