Re: proposal: PL/Pythonu - function ereport

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: proposal: PL/Pythonu - function ereport
Дата
Msg-id CAFj8pRAimXv+MAez-VXKm=2qhrs0yCML38d=BJH_o8mMaprHFQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: proposal: PL/Pythonu - function ereport  (Teodor Sigaev <teodor@sigaev.ru>)
Ответы Re: proposal: PL/Pythonu - function ereport
Список pgsql-hackers


2015-11-27 17:54 GMT+01:00 Teodor Sigaev <teodor@sigaev.ru>:
Is this patch in 'Waiting on Author' state actually?

yes

I'll try redesign patch by Peter's proposal

Pavel
 


     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?

I think plpy.Error is fine.




--
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                   WWW: http://www.sigaev.ru/

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

Предыдущее
От: Teodor Sigaev
Дата:
Сообщение: Re: proposal: PL/Pythonu - function ereport
Следующее
От: XiaoChuan Yu
Дата:
Сообщение: How to add and use a static library within Postgres backend