Re: pl/python custom exceptions for SPI

From: Hannu Krosing <hannu(at)2ndquadrant(dot)com>
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-01-10 23:21:28
Message-ID: 4D2B9478.3080405@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10.1.2011 17:20, Jan Urbański wrote:
> On 23/12/10 15:40, Jan Urbański wrote:
>> Here's a patch implementing custom Python exceptions for SPI errors
>> mentioned in
>> http://archives.postgresql.org/pgsql-hackers/2010-12/msg01991.php. It's
>> an incremental patch on top of the explicit-subxacts patch sent eariler.
> I changed that patch to use Perl instead of sed to generate the
> exceptions, which should be a more portable.
Why not python ?
> It's still not nice, and I
> think the way forward is to have a common format for SQLSTATE
> conditions, as proposed in
> http://archives.postgresql.org/message-id/4D19C93C.5000703@wulczer.org.
>
> I failed to follow on with that patch because I couldn't figure out how
> to persuade the buildsystem to generate errcodes.h early enough for the
> rest of the system to compile, not to mention doing it for the MSVC
> build system.
>
> Cheers,
> Jan
>
>
>

--
--------------------------------------------
Hannu Krosing
Senior Consultant,
Infinite Scalability& Performance
http://www.2ndQuadrant.com/books/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shigeru HANADA 2011-01-10 23:21:53 Re: SQL/MED - file_fdw
Previous Message Lukas Eder 2011-01-10 23:06:31 Weird issues when reading UDT from stored function