| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: User's exception plpgsql |
| Date: | 2005-07-26 01:41:10 |
| Message-ID: | 42E594B6.7020603@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Emmerton | 2005-07-26 02:03:48 | Re: ORDER BY <field not in return list> |
| Previous Message | Jeff Davis | 2005-07-26 01:14:48 | Re: [HACKERS] Enticing interns to PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2005-07-26 04:48:36 | Re: User's exception plpgsql |
| Previous Message | Michael Glaesemann | 2005-07-26 00:52:48 | Interval->day docs and regression tests |