| From: | Uwe Bartels <uwe(dot)bartels(at)gmail(dot)com> |
|---|---|
| To: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: plpgsql exception handling |
| Date: | 2011-03-10 10:53:55 |
| Message-ID: | AANLkTimhffg2cNb9gqU8X2Q6GupRKKEtEkPK6i3h2AUp@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
same same.
all errors including syntax_error match to others, but I checked it again.
and the exception remains.
Uwe
On 10 March 2011 10:56, Samuel Gendler <sgendler(at)ideasculptor(dot)com> wrote:
>
>
> On Thu, Mar 10, 2011 at 12:45 AM, Uwe Bartels <uwe(dot)bartels(at)gmail(dot)com>wrote:
>
>> Hi,
>>
>> Yes, of course is this sql producing an error.
>> The point is, I want to trap the error and handle it. Here in this case I
>> set the variable l_state and l_message.
>>
>
>
> Doh! Of course. Sorry about that. What happens when you explicitly catch
> the 42601 sql state or the syntax_error condition instead of 'others?'
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Samuel Gendler | 2011-03-10 18:27:09 | Re: plpgsql exception handling |
| Previous Message | Samuel Gendler | 2011-03-10 09:56:45 | Re: plpgsql exception handling |