From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Catalin Iacob <iacobcatalin(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: PL/Pythonu - function ereport |
Date: | 2015-11-27 16:54:37 |
Message-ID: | 56588ACD.90005@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-11-27 16:57:04 | Re: proposal: PL/Pythonu - function ereport |
Previous Message | Tom Lane | 2015-11-27 16:35:29 | Re: Redefine default result from PQhost()? |