From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: cutting out the middleperl |
Date: | 2007-03-27 16:52:26 |
Message-ID: | 6711CF45-7EF0-468D-90EF-5AC2C1EC2275@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mar 27, 2007, at 7:34 AM, Aidan Van Dyk 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
Or SQL-on-rails
http://www.sqlonrails.org/
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2007-03-27 16:56:58 | Re: Strange behaviour under heavy load |
Previous Message | Scott Marlowe | 2007-03-27 16:51:15 | Re: Is there a shortage of postgresql skilled ops people |