From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, David Fetter <david(at)fetter(dot)org>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Wishlist of PL/Perl Enhancements for PostgreSQL 8.5 |
Date: | 2009-10-06 18:18:33 |
Message-ID: | 20091006181833.GP5929@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Filip Rembiałkowski escribió:
> 2009/10/6 Richard Huxton <dev(at)archonet(dot)com>
>
> >
> > Are we looking down the wrong end of the telescope here? What if we had
> > something more like the "C" binding for functions:
> >
> > CREATE FUNCTION foo(int,text,int) AS 'MyModule::internal_foo' LANGUAGE
> > plperl;
>
> > If you want inter-function calls you use internal_foo.
> >
> this really would be a great feature for many plperl users.
> ( I'm not sure how it breaks current PL model in postgres)
This would be a pain for dumps, because the user would have to install
the modules separately. Maybe we could have a different language (say
plperl2 for lack of a better name) that could work this way; if you
really wanted to do this, you could.
Having plperl functions as separate files would be great for stuff like
syntax coloring in editors.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Sachin Srivastava | 2009-10-06 19:09:11 | Re: initdb failing |
Previous Message | Raymond O'Donnell | 2009-10-06 18:11:47 | Re: initdb failing |