Re: Schema w/o alter table privs.

One way around this is to use (2) schemas. One (call it app_owner) owns all the typical DB objects (tables, views, sequences, packages, etc). The other (call it app_user) just contains synonyms to the app_owner objects. You need to have grants for the appropriate permissions (select, insert, update, delete, execute) granted from app_owner to app_user on each required object.

There is some administration burden in keeping the (2) accounts synchronized, but this gives you the isolation from DDL activities and requires no change to the applications.

-Peter

VWP914 wrote:
>
> Is it possible to create a schema that people can connect to, yet do not have
> the ability to alter the tables? We have a very "open" database working
> environment, but I am sick and tired of have certain people adding columns to
> tables w/o running it by the people it affects! It seems to me that once you
> are able to connect, you are in effect logged in as the owner of the schema
> objects and can do whatever you want with them. Is there any way of ensuring
> that people can't alter the tables when they are logged in to a certain schema?
>
> Any help would be appreciated.
>
> Thomas
Received on Tue Feb 05 2002 - 07:53:02 CST