From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposed TODO: add support for "any" for PL/PythonU and PL/Perl |
Date: | 2013-05-15 11:04:37 |
Message-ID: | CA+TgmobwdyVcOC+F_9TpM7Gq1R2ep5sA6wABZSvdpqNxOoSZgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 14, 2013 at 2:24 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Hackers,
>
> I'd like to add the following todo items to the TODO list:
>
> PL/Python:
> * add support for anyelement and anyarray to PL/Python
> * add support for VARIADIC "ANY" to PL/Python
>
> PL/Perl:
> * add support for anyelement and anyarray to PL/Perl
> * add support for VARIADIC "ANY" to PL/Perl
>
> The reason for this is that both Python and Perl are loosely typed
> languages, and deal with variables as polymorphic. Mapping Postgres
> polymorphic parameters to functions in these PLs couldn't be more
> natural. I know from my part that support for VARIADIC "ANY" in
> PL/Python would save me a bunch of shell function writing.
>
> I don't personally intend to hack these out, but they seem like good
> things to put on the TODO list as good tasks for new hackers (and maybe
> GSOC students) to take on.
+1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-05-15 11:08:55 | Re: Proposed TODO: add support for "any" for PL/PythonU and PL/Perl |
Previous Message | Robert Haas | 2013-05-15 10:59:16 | Re: Logging of PAM Authentication Failure |