First I want to thank those who responded to my last inquiry with
some great help/resources.
I created a policy function based upon subject to restrict users from
updating, inserting or deleting schedule data if not in their subject
area(s). I added the policy (DBMS_RLS.ADD_POLICY). And then I
tested it:
SQL > CONNECT auser Enter password: Connected. SQL> SELECT COUNT(*) 2 FROM CLASS_SCHEDULE 3 WHERE TERM_CODE = '200402' 4 AND SUBJECT_CODE = 'SPAN';
COUNT(*) ---------- 32
SQL> DELETE 2 FROM CLASS_SCHEDULE 3 WHERE TERM_CODE = '200402' 4 AND SUBJECT_CODE = 'SPAN';
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Daniel P. Looby email: dan.looby@xxxxxxxxxxxxxx Lead Systems Analyst Enterprise Information Systems/OIT A meeting is an event at Georgia Institute Of Technology which minutes are kept 845 Marietta Street and hours are lost! Atlanta, GA 30332-0305 Office Phone: 404-894-9587 Fax: 404-894-8945 ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------