Re: Proposed TODO: add support for "any" for PL/PythonU and PL/Perl - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Proposed TODO: add support for "any" for PL/PythonU and PL/Perl
Date
Msg-id CA+TgmobwdyVcOC+F_9TpM7Gq1R2ep5sA6wABZSvdpqNxOoSZgw@mail.gmail.com
Whole thread Raw
In response to Proposed TODO: add support for "any" for PL/PythonU and PL/Perl  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Proposed TODO: add support for "any" for PL/PythonU and PL/Perl  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Tue, May 14, 2013 at 2:24 PM, Josh Berkus <josh@agliodbs.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Logging of PAM Authentication Failure
Next
From: Pavel Stehule
Date:
Subject: Re: Proposed TODO: add support for "any" for PL/PythonU and PL/Perl