Re: User's exception plpgsql - Mailing list pgsql-patches

From Neil Conway
Subject Re: User's exception plpgsql
Date
Msg-id 42E594B6.7020603@samurai.com
Whole thread Raw
In response to Re: User's exception plpgsql  (Neil Conway <neilc@samurai.com>)
Responses Re: User's exception plpgsql  (Pavel Stehule <stehule@kix.fsv.cvut.cz>)
Re: User's exception plpgsql  (Pavel Stehule <stehule@kix.fsv.cvut.cz>)
List pgsql-patches
Neil Conway wrote:
> Not at the moment. I believe we have agreed that it would be better to
> remove the concept of "exception variables" and just use strings, but I
> haven't implemented this yet.

BTW, one minor annoyance I noticed: a builtin condition name can
actually map to multiple SQLSTATE values. If we allow a builtin
condition name to be specified to RAISE, this means we'll actually need
to pass around a list of SQLSTATE values that are thrown by the RAISE,
rather than a single SQLSTATE. This seems pretty ugly, though --
especially considering that only a handful of the builtin condition
names actually do map to multiple SQLSTATEs. Does anyone have a better
suggestion?

-Neil

pgsql-patches by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: [HACKERS] Patch to fix plpython on OS X
Next
From: Michael Glaesemann
Date:
Subject: Interval->day docs and regression tests