| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Sibtay Abbas <sibtay_abbas(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: exception handling in plpgsql |
| Date: | 2004-12-31 23:02:36 |
| Message-ID: | 41D5DA8C.9000806@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Fuhr wrote:
>On Fri, Dec 31, 2004 at 03:18:39PM -0500, Andrew Dunstan wrote:
>
>
>
>>It has told you what the problem is. Use a handler for an exception that
>>actually exists. To see what these are, read
>>http://developer.postgresql.org/docs/postgres/plpgsql-errors-and-messages.html
>>
>>
>
>As the PL/pgSQL "Trapping Errors" documentation says, "The _condition_
>names can be any of those shown in Appendix A," so a more useful link
>would be:
>
>http://developer.postgresql.org/docs/postgres/errcodes-appendix.html
>
>
You are right. My humble apologies.
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-01-01 00:42:20 | Re: 'COPY ... FROM' inserts to btree, blocks on buffer writeout |
| Previous Message | Michael Fuhr | 2004-12-31 22:44:00 | Re: exception handling in plpgsql |