Re: plpgsql exception handling
| От | Uwe Bartels |
|---|---|
| Тема | Re: plpgsql exception handling |
| Дата | |
| Msg-id | AANLkTinqWVVtCn4FO49G-22xQoqvXsRrbDMZ1JhzO4Xa@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: plpgsql exception handling (Uwe Bartels <uwe.bartels@gmail.com>) |
| Список | pgsql-sql |
stupid me.
I edited a function with the same name, but different parameter types and tested with the other function.
so everything works fine.
thanks everybody for help.
best regards,
Uwe
I edited a function with the same name, but different parameter types and tested with the other function.
so everything works fine.
thanks everybody for help.
best regards,
Uwe
On 10 March 2011 11:53, Uwe Bartels <uwe.bartels@gmail.com> wrote:
same same.
all errors including syntax_error match to others, but I checked it again. and the exception remains.
UweOn 10 March 2011 10:56, Samuel Gendler <sgendler@ideasculptor.com> wrote:On Thu, Mar 10, 2011 at 12:45 AM, Uwe Bartels <uwe.bartels@gmail.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?'
В списке pgsql-sql по дате отправления: