On 29 October 2010 18:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Sergey Konoplev <gray.ru@gmail.com> writes:
>> On 29 October 2010 17:02, Dragos Valentin Moinescu
>> <dragos.moinescu@gmail.com> wrote:
>>> The thing is that I cannot catch the exception raised by plpy.execute().
>
>> I came to this plpython function template. It handles errors properly
>> and works faster then usual function because of the code caching.
>
> Really? As far as I can see, it's entirely impossible for a plpython
> function to trap and recover from an error in plpy.execute. It can
> continue to run plain python code, but it won't be allowed to call
> plpy.execute again, and the error will be rethrown when control exits
> the function. There's no way to fix that short of setting up
> subtransactions, which is what the other PLs do.
Oh I am sorry for bothering you and other members. I have not read the
problem properly - my fault.
>
> regards, tom lane
>
--
Sergey Konoplev
Blog: http://gray-hemp.blogspot.com /
Linkedin: http://ru.linkedin.com/in/grayhemp /
JID/GTalk: gray.ru@gmail.com / Skype: gray-hemp
