| From: | "Bart Degryse" <Bart(dot)Degryse(at)indicator(dot)be> |
|---|---|
| To: | "Alex Hochberger" <alex(at)dsgi(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: pl/pgsql and error handling |
| Date: | 2008-02-29 07:44:03 |
| Message-ID: | 47C7C5D3.A3DD.0030.0@indicator.be |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
www.postgresql.org/docs/8.2/static/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING would be the place to look.
>>> Alex Hochberger <alex(at)dsgi(dot)us> 2008-02-29 6:29 >>>
I do not know. It's sounds like the Oracle PL/SQL behavior is what I
want. Does PostgreSQL's pl/pgsql have such a feature? It's not in
the documentation anywhere. I'll check it from the office tomorrow.
Alex
On Feb 28, 2008, at 11:43 PM, Tom Lane wrote:
> Alex Hochberger <alex(at)dsgi(dot)us> writes:
>> Is it possible to grab access to the actually user-friendly error
>> message?
>
> Doesn't the SQLERRM variable do what you want?
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org ( http://archives.postgresql.org/ )
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Professor Flávio Brito | 2008-03-01 11:11:37 | Function returns error (view) (RESOLVED) |
| Previous Message | Alex Hochberger | 2008-02-29 05:29:25 | Re: pl/pgsql and error handling |