Re: create user/role with read only access?

Or, create public synonyms(with the same names as the app. tables) on the app tables and then grant select on these synonyms to a role or any specific user. In this way, the fully qualified reference(owner.table), is not required from within other schema.

Ali88

"Terry Dykstra" <dontreply_tdykstra_at_cfol.ab.ca> wrote in message news:fDWm6.1991$pF4.161323_at_news1.telusplanet.net...
> give him connect & create session privilege. Then (directly or through a
> default role) grant him select on the application tables. No need to
 grant
> 'select any table'. As the application owner, just do:
>
> select 'grant select on ' || table_name || ' to theuser;'
> from user_tables
>
> spool this to a file and you have a quick way of granting the user select
> privileges on all tables.
>
> --
> Terry Dykstra
> Canadian Forest Oil Ltd.
> "Rob Williamson" <robw_at_physics.umd.edu> wrote in message
> news:3A9C2378.8E0DEFBE_at_physics.umd.edu...
> > how do I create a user and give him only permission to do selects
> > on tables but not allow him to change anything?
> > I believe the select on any table permission allows 2
> > things I might not like.
> > 1) select sequence.nextval from dual;
> > ** changing a sequence to a new value might not be a desired
> > permission
> >
> > 2) I believe I read that this also gives them the ability to use the
> > lock table
> > command which could cause trouble
> >
> > *** the user wants to use MS Access as the front end to write reports
> > so I was worried maybe Access could lock up the tables in some way I
> > was
> > not intending.
> >
> > Any other possible problems?
> >
> >
> > Thanks in advance.
> >
> > Rob
>
>
>
Received on Tue Feb 27 2001 - 22:34:10 CST