Re: proposal: PL/Pythonu - function ereport

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/