|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Oracle’s new fine-grained access control mechanism has had several names. It is also known as Virtual Private Database (VPD), and row-level security. The benefits of row-level security include:
As we may know, Oracle has three ways to control data access:
When users access a table (or view) that has a security policy, the Oracle server calls the policy function, which returns a “predicate.” A predicate is a WHERE clause that qualifies a particular set of rows within the table. Oracle8i then dynamically rewrites the query by appending the predicate to users' SQL statements. While policies provide row-level access control, you can do the same thing without policies by creating custom views on the target tables: create or replace view acctg_view as select * from emp where job=‘ACCOUNTING’; create or replace view clerk_view as select * from emp where job=‘CLERK’; grant acctg_view to acctg_role; grant clerk_view to clerk_role; If you like Oracle tuning, you might enjoy my latest book “Oracle Tuning: The Definitive Reference” by Rampant TechPress. It’s only $41.95 (I don’t think it is right to charge a fortune for books!) and you can buy it right now at this link: http://www.rampant-books.com/book_2003_1_oracle9i_sga.htm
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Copyright © 1996 - 2009 by
Burleson Enterprises, Inc. All rights reserved.
Oracle® is the registered trademark
of Oracle Corporation. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||