| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Nathan Boley <npboley(at)gmail(dot)com> |
| Cc: | 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 20:35:39 |
| Message-ID: | 1265056539.30433.4.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-01 20:42:02 | Re: [PATCH] Provide rowcount for utility SELECTs |
| Previous Message | Nathan Boley | 2010-02-01 20:23:21 | Re: plpython3 |