Re: cutting out the middleperl

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Aidan Van Dyk" <aidan(at)highrise(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org, help(at)asmith(dot)id(dot)au
Subject: Re: cutting out the middleperl
Date: 2007-03-29 19:48:14
Message-ID: b42b73150703291248s7477d9a3x3b2ac553eb5b803e@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/27/07, Aidan Van Dyk <aidan(at)highrise(dot)ca> wrote:
> Kev wrote:
>
> > Hi everyone,
> >
> > I'm still in the design phase of a project. I was just wondering if
> > anyone has any thoughts or experience on the idea of cutting the P out
> > of the LAMP (or in my case, WAMP for now) stack. What I mean is
> > having
> > everything encapsulated into sql (or plpgsql or plperl where needed)
> > functions stored in the pgsql server, and have Apache communicate with
> > pgsql via a tiny C program that pretty much just checks whether the
> > incoming function is on the allowed list and has the proper data
> > types,
> > then passes it straight in. Any errors are logged as potential
> > security
> > breaches.
>
> Sounds something like mod_libpq:
> http://asmith.id.au/mod_libpq.html

brilliant. highest possible marks! i mean, wow! :-)

merlin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Benjamin Arai 2007-03-29 19:51:38 Re: COPY command details
Previous Message Tom Lane 2007-03-29 19:46:12 Re: Some encoding trouble via libpq