On 11/15/15 11:29 PM, Pavel Stehule wrote: > > > 2015-11-16 5:20 GMT+01:00 Peter Eisentraut <pete...@gmx.net > <mailto:pete...@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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
