| From: | Wiebe Cazemier <halfgaar(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Trapping errors from pl/perl (trigger) functions |
| Date: | 2007-07-01 22:07:14 |
| Message-ID: | f698ij$jt0$1@sea.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sunday 01 July 2007 21:50, Tom Lane wrote:
> Why would you expect it to? The raise_exception SQLSTATE applies
> specifically and solely to the plpgsql RAISE command. The entire
> point of those identifiers is to match fairly narrow classes of
> exceptions, not anything thrown by anyone.
>
> IMHO the real problem with both RAISE and the plperl elog command
> is there's no way to specify which SQLSTATE to throw. In the case
> of the elog command I think you just get a default.
I expected it to, because I told elog what kind of errorlevel to give me, but
apparently that does not influence the SQLSTATE. I didn't know it didn't apply
to procedures in other languages.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D. Dante Lorenso | 2007-07-01 22:09:38 | How do I aggregate data from multiple rows into a delimited list? |
| Previous Message | Michael Fuhr | 2007-07-01 21:53:30 | Re: Trapping errors from pl/perl (trigger) functions |