Hi Lonnie,
This is one of the reasons we are moving to an EJB server at work (we're
using Oracle there, but they wanted to accomplish the same thing you want
to do with Postgres). By exposing specialized interfaces to the db we
effectively limit the types of queries that can be run. That might be
more overhead than you want to deal with in your application, but for us
it makes sense because we have so many different types of applications
hitting the db (servlets and JSP pages, Swing applications, perl scripts,
C programs, etc...)
-M@
--
There are more things in heaven and earth,
Horatio, than are dreamt of in your philosophy.
On Fri, 20 Apr 2001, Lonnie Cumberland wrote:
> Hello All,
>
> We are developing an application that will allow our websites to talk to our
> database.
>
> In the interest of security, I am wondering if it is possible to turn off some
> of the functions in the SQL command list such that a user can only communicate
> to the database through our functions.
>
> What I mean is this. We have built a number of "C" extensions and PL/pgSQL
> proceedures that will work on our database, but I only want to allow an outside
> query to only one or two of our selected entry points.
>
> The webserver interface query statement might, for example, be able to only
> call "select register_user(.......)" or "select login_user(....)" and NONE of
> the other PostgreSQL command functions.
>
> I only want to allow access to these functions from the outside world, but the
> server needs to be able to execute all of the original functions without
> restrictions.
>
> Any information on this would be greatly appreciated,
> Lonnie
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>