Xref: alice comp.databases.oracle.server:83060
Path: alice!news-feed.fnsi.net!enews.sgi.com!newsfeed.mathworks.com!newsfeed.enteract.com!netnews.com!newspeer1.nac.net!news.maxwell.syr.edu!nntp2.deja.com!nnrp1.deja.com!not-for-mail
From: cosmin_ioan@msn.com
Newsgroups: comp.databases.oracle.server
Subject: Role Usage qq
Date: Wed, 02 Feb 2000 15:03:05 GMT
Organization: Deja.com - Before you buy.
Lines: 27
Message-ID: <879gv6$g1e$1@nnrp1.deja.com>
X-Article-Creation-Date: Wed Feb 02 15:03:05 2000 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT)
X-Http-Proxy: 1.1 x36.deja.com:80 (Squid/1.1.22) for client 199.227.24.2
X-MyDeja-Info: XMYDJUIDcosmin_ioan

hello all,

We are debating an issue with the DBA and the developers regarding
usage of the roles.

Basically, one side says that we should create different roles with
different priviledge on all the packages, that is, let's say Role A has
select privilege on all packages, while role B has only insert
privilege on all packages.

Now, there's the other party that says, give all (or some) privileges
to Role A of **only** specific packages, and give Role B all (or some)
privileges on **other packages**, different then Role A.

As far as I can see it, there's nothing wrong with either technique, it
is the same as viewing security under different **lenses** (just like
viewing a database structure at the logical vs. physical level).

Is any particular view wrong here (or less efficient)!?

Thank you very much,

Cosmin


Sent via Deja.com http://www.deja.com/
Before you buy.
