From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: plperl direction |
Date: | 2001-06-18 17:59:20 |
Message-ID: | 200106181759.f5IHxKV13801@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Just wanted to share with y'all what I wanna do with plperl:
>
> 1) I want to implement database access from plperl script by providing a
> perl module DBD::PgSPI which instead of using libpq interface to talk to
> database would use SPI. Thus, certain client-side scripts could become
> stored procedures with no change of code.
>
> 2) When that's done, it'll be possible to have an 'application server'
> running as an frontend to postgresql. An external program would take SOAP
> (or CORBA or something) calls and translate them to calls of plperl stored
> procedures. Since perl procedures are able to return complex data
> structures, and methods to marshal them are easily available, such
> procedure can encapsulate business logic in one place. Also, an neat
> possibility is client providing perl code to process things to the server
> (where SQL just won't do).
>
> 3) Possibly, later, the 'external program' described above could be merged
> into postgresql proper, to achieve additional speedup.
This all sounds good to me.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-06-18 18:04:32 | Re: timestamp with/without time zone |
Previous Message | Bruce Momjian | 2001-06-18 17:56:05 | Re: [PATCH] untrusted plperl |