From: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | 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-08 04:39:13 |
Message-ID: | Pine.LNX.4.44.0507080636140.1715-100000@kix.fsv.cvut.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Fri, 8 Jul 2005, Neil Conway wrote:
> Neil Conway wrote:
> > Ah, I see. I would be content to allow opt_sqlstate to be either a
> > string literal, a T_WORD (predefined error condition), or a TEXT
> > variable. If users need to throw a sqlstate that is derived from a SQL
> > expression, they can always assign to a TEXT variable and then specify
> > that variable to RAISE.
>
> >>> RAISE [ opt_sqlstate ] LEVEL 'fmt' [ , expr ... ]
>
> BTW, do have we reached a consensus on this?
>
> -Neil
>
ok, but don't forget, please, on exception part.
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2005-07-08 04:49:58 | Re: User's exception plpgsql |
Previous Message | Tom Lane | 2005-07-08 04:38:47 | Re: User's exception plpgsql |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2005-07-08 04:49:58 | Re: User's exception plpgsql |
Previous Message | Tom Lane | 2005-07-08 04:38:47 | Re: User's exception plpgsql |