Skip site navigation (1) Skip section navigation (2)

Re: plpython3

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Nathan Boley <npboley(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>,James William Pye <lists(at)jwp(dot)name>,Greg Smith <greg(at)2ndquadrant(dot)com>, jd(at)commandprompt(dot)com,Josh Berkus <josh(at)agliodbs(dot)com>,PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpython3
Date: 2010-02-01 21:11:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Peter Eisentraut escribió:
> On mån, 2010-02-01 at 12:01 -0800, Nathan Boley wrote:
> > I code nearly exclusively in python and C, but I have
> > often found pl/python to be very unwieldy.  For this reason I often
> > use pl/perl or pl/pgsql for problems that, outside of postgres, I
> > would always use python.
> I find that curious, because much of the criticism about the current
> PL/Python can be traced back to the fact that the implementation used to
> be an exact copy of PL/Perl.

Perhaps the problem is that PL/Perl used to be unwieldy back when
PL/Python was created.  PL/Perl has definitely seen a lot more activity.

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2010-02-01 21:13:39
Subject: Re: plpython3
Previous:From: Joshua D. DrakeDate: 2010-02-01 20:57:54
Subject: Re: plpython3

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group