| From: | gherzig(at)fmed(dot)uba(dot)ar |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: calling EXECUTE on any exception |
| Date: | 2005-07-29 15:59:28 |
| Message-ID: | 2081.157.92.152.3.1122652768.squirrel@www.webmail.fmed.uba.ar |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Oh...to bad...Thank you Michael!
Did someone know if it can be acomplished in pypgsql?
Thanks againg falks.
Gerardo
> On Fri, Jul 29, 2005 at 10:36:52AM -0300, gherzig(at)fmed(dot)uba(dot)ar wrote:
>> EXCEPTION
>> WHEN OTHER THEN
>> EXECUTE exception_handler(Exception_code)
>>
>> how do i get that error_code (or code_name, whatever i can get)
>> generated in the something() function to be proccesed by the
>> exception_handler() function?
>
> I don't think you can do this in released versions of PostgreSQL.
> In 8.1 you'll be able to use SQLSTATE to get the error code and
> SQLERRM to get the error message.
>
> --
> Michael Fuhr
> http://www.fuhr.org/~mfuhr/
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Boes | 2005-07-29 17:09:48 | CREATE TABLE AS SELECT |
| Previous Message | Richard Huxton | 2005-07-29 15:42:48 | Re: Why are these queries so different in time? |