| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dragos Valentin Moinescu <dragos(dot)moinescu(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: plpythonu: how to catch plpy.execute() exceptions |
| Date: | 2010-10-29 16:27:21 |
| Message-ID: | 1288369641.2355.17.camel@jd-desktop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 2010-10-29 at 10:03 -0400, Tom Lane wrote:
> Dragos Valentin Moinescu <dragos(dot)moinescu(at)gmail(dot)com> writes:
> > The thing is that I cannot catch the exception raised by plpy.execute().
>
> Yeah, plpython's error handling is fundamentally broken. Somebody
> needs to rewrite it to be more like the other PLs. In the meantime,
> I'd suggest using plperl, which has gotten a lot more love than
> plpython ever did.
Or take a look at pg-python:
http://pgfoundry.org/projects/python/
Which is much more actively maintained and still Python.
JD
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerhard Hintermayer | 2010-10-29 16:41:36 | Re: Minor upgrade procedure while DB up & running |
| Previous Message | Sergey Konoplev | 2010-10-29 14:55:29 | Re: plpythonu: how to catch plpy.execute() exceptions |