If you can find the earlier thread, you will see that
the feature you need has already been added to 7.3
development code. You may be able to patch that into
your 7.2 installation. A participant in that
discussion has probably already tested it.
--- "Lars Preben S. Arnesen" <l.p.arnesen@usit.uio.no>
wrote:
> [ Doug McNaught ]
>
> > We had a nice little flamewar about this a few
> weeks ago. ;)
>
> OK. I'll look into the arguments in the war...
>
> > The "Postgres" way to do it is to lock the
> unprivileged user out of
> > the "real" tables, and create views for that user
> to access. The
> > views can include only the fields that you want
> them to see, and you'd
> > create ON INSERT/DELETE/UPDATE rules to validate
> input and write to
> > the actual tables.
>
> Hmmm. I'm not going to start another flame war, but
> I think this seems
> like it could be somewhat easier with the Oracle
> solution (at least
> what I have heard from Oracle-users) that enables
> you to restrict a
> database user only to execute predefined functions.
>
> As I understand it I need to create functions, views
> and triggers to
> get what I want.
>
> > This is kind of a different way of thinking about
> it than the "proxy
> > functions" concept but you should be able to do
> everything you want to
> > do.
>
> With programming, everything is possible. :)
>
> --
> Lars Preben
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please
> send an appropriate
> subscribe-nomail command to majordomo@postgresql.org
> so that your
> message can get through to the mailing list cleanly
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/
