| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: User's exception plpgsql |
| Date: | 2005-07-08 04:32:16 |
| Message-ID: | 42CE01D0.8060700@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-08 04:38:47 | Re: User's exception plpgsql |
| Previous Message | Tom Lane | 2005-07-08 04:12:41 | Re: Checkpoint cost, looks like it is WAL/CRC |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-08 04:38:47 | Re: User's exception plpgsql |
| Previous Message | Neil Conway | 2005-07-08 04:28:10 | Re: pgcrypto volatility and strictness changes |