Re: proposal: PL/Pythonu - function ereport

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: proposal: PL/Pythonu - function ereport
Дата
Msg-id 564A5B46.1000807@gmx.net
обсуждение исходный текст
Ответ на Re: proposal: PL/Pythonu - function ereport  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: proposal: PL/Pythonu - function ereport
Re: proposal: PL/Pythonu - function ereport
Список pgsql-hackers
On 11/15/15 11:29 PM, Pavel Stehule wrote:
> 
> 
> 2015-11-16 5:20 GMT+01:00 Peter Eisentraut <peter_e@gmx.net
> <mailto: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?

I think plpy.Error is fine.




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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: pg_hba_lookup function to get all matching pg_hba.conf entries
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [PATCH] SQL function to report log message