Re: Trapping errors from pl/perl (trigger) functions

Поиск
Список
Период
Сортировка
От Wiebe Cazemier
Тема Re: Trapping errors from pl/perl (trigger) functions
Дата
Msg-id f698ij$jt0$1@sea.gmane.org
обсуждение исходный текст
Ответ на Trapping errors from pl/perl (trigger) functions  (Wiebe Cazemier <halfgaar@gmx.net>)
Список pgsql-general
On Sunday 01 July 2007 21:50, Tom Lane wrote:

> Why would you expect it to?  The raise_exception SQLSTATE applies
> specifically and solely to the plpgsql RAISE command.  The entire
> point of those identifiers is to match fairly narrow classes of
> exceptions, not anything thrown by anyone.
>
> IMHO the real problem with both RAISE and the plperl elog command
> is there's no way to specify which SQLSTATE to throw.  In the case
> of the elog command I think you just get a default.

I expected it to, because I told elog what kind of errorlevel to give me, but
apparently that does not influence the SQLSTATE. I didn't know it didn't apply
to procedures in other languages.

В списке pgsql-general по дате отправления:

Предыдущее
От: Michael Fuhr
Дата:
Сообщение: Re: Trapping errors from pl/perl (trigger) functions
Следующее
От: David Fetter
Дата:
Сообщение: Re: [pgsql-general] In memory tables/databases