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

From Peter Eisentraut
Subject Re: proposal: PL/Pythonu - function ereport
Date
Msg-id 564959A8.4040203@gmx.net
Whole thread Raw
In response to Re: proposal: PL/Pythonu - function ereport  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: PL/Pythonu - function ereport  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_hba_lookup function to get all matching pg_hba.conf entries
Next
From: Etsuro Fujita
Date:
Subject: Re: Foreign join pushdown vs EvalPlanQual