| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Select Any Table : Pros and Cons.
Nik
I don't see where anyone has responded yet, but the list has been acting
flaky lately.
In general, beware of granting privileges named "ANY". I would strongly favor creating a role, granting select on all needed tables to that role, then granting the role to the developers. I'm guessing that today this database does not contain any information that is private from any developers. But you never know about tomorrow. You may incorporate a new schema and forget the developers have this privilege. I haven't tested this, but I'm guessing if this database has any links to other databases, a clever developer might be able to see enough information to figure out how to get to that other system. Just strikes me as poor practice.
Dennis Williams
DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of H elp_me
Sent: Friday, May 14, 2004 2:39 PM
To: oracle-l_at_freelists.org
Subject: Select Any Table : Pros and Cons.
Hello, Can someone list me the pros and cons of SELECT ANY TABLE priviligeto Developers in Test and Production Databases. Thanks in Advance. Nik
 |
 |