Re: proposal: PL/Pythonu - function ereport

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: proposal: PL/Pythonu - function ereport
Дата
Msg-id CAFj8pRDFnCE5x80CY-LNGamy71FwKG81ucFZ5amd8ax0D9vWEQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: proposal: PL/Pythonu - function ereport  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: proposal: PL/Pythonu - function ereport  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers


2015-11-16 5:20 GMT+01:00 Peter Eisentraut <peter_e@gmx.net>:
I don't think it's right to reuse SPIError for this.  SPIError is
clearly meant to signal an error in the SPI calls.  Of course, we can't
stop users from raising whatever exception they want, but if we're going
to advertise that users can raise exceptions, then we should create
separate exception classes.

I suppose the proper way to set this up would be to create a base class
like plpy.Error and derive SPIError from that.

Do you have some ideas about the name of this class?

Regards

Pavel

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

Предыдущее
От: Etsuro Fujita
Дата:
Сообщение: Re: Foreign join pushdown vs EvalPlanQual
Следующее
От: dinesh kumar
Дата:
Сообщение: Re: [PATCH] SQL function to report log message