Re: proposal: PL/Pythonu - function ereport - Mailing list pgsql-hackers

From Teodor Sigaev
Subject Re: proposal: PL/Pythonu - function ereport
Date
Msg-id 56588ACD.90005@sigaev.ru
Whole thread Raw
In response to Re: proposal: PL/Pythonu - function ereport  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: proposal: PL/Pythonu - function ereport  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Is this patch in 'Waiting on Author' state actually?

>>      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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: Redefine default result from PQhost()?
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: PL/Pythonu - function ereport