On 31/01/11 00:03, Jan Urbański wrote:
> On 29/01/11 22:13, Jan Urbański wrote:
>> On 29/01/11 22:10, Steve Singer wrote:
>>> On 11-01-29 03:39 PM, Jan Urbański wrote:
>>>> D'oh, you're right, thanks. Attached patch with fix. Curiosly, right now
>>>> in master your example with plpy.prepare will result in "savepoint"
>>>> being swallowed, but it's of course better to react with an error.
>>> This seems to fix it.
>>> You mentioned that you were going to add a few paragraphs to the
>>> documentation saying that you can now actually catch SPI errors. I
>>> haven't seen that yet.
>> Yeah, I'm procrastinating the doc writing part ;) Will spit something
>> out by the end of the (CET) day.
> Done, added a small example in the Database Access section.
... aaand another one. I'll never get used to the way section titles are
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2011-01-30 23:19:54|
|Subject: Re: autogenerating error code lists (was Re: [COMMITTERS] pgsql: Add foreign data wrapper error code values for SQL/MED.) |
|Previous:||From: Jan Urbański||Date: 2011-01-30 23:03:25|
|Subject: Re: pl/python SPI in subtransactions|