From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
Cc: | Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pl/python custom exceptions for SPI |
Date: | 2011-02-10 19:24:16 |
Message-ID: | 1297365856.27142.8.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On sön, 2011-02-06 at 20:44 +0100, Jan Urbański wrote:
> On 27/01/11 23:24, Jan Urbański wrote:
> > On 11/01/11 12:20, Jan Urbański wrote:
> >> On 11/01/11 01:27, Tom Lane wrote:
> >>> Hannu Krosing <hannu(at)2ndquadrant(dot)com> writes:
> >>>> On 10.1.2011 17:20, Jan Urbański wrote:
> >>>>> I changed that patch to use Perl instead of sed to generate the
> >>>>> exceptions, which should be a more portable.
> >
> > Updated as an incremental patch on to of the recently sent version of
> > explicit-subxacts.
>
> Updated again.
Why do the error messages print spiexceptions.SyntaxError instead of
plpy.spiexceptions.SyntaxError? Is this intentional or just the way it
comes out of Python?
Please add some documentation. Not a list of all exceptions, but at
least a paragraph that various kinds of specific exceptions may be
generated, what package and module they are in, and how they relate.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-02-10 19:31:09 | Re: ALTER EXTENSION UPGRADE, v3 |
Previous Message | Tom Lane | 2011-02-10 19:21:03 | Re: Range Type constructors |