row security

Hi,
I have several tables to which I want to restrict user access. That is, different users should see (select, update, delete, insert) different rows. My current thinking is to give users no access to the tables, build views for each of the tables, and create a trigger on insert. The views will determine what any given user can select, update, and delete; and the triggers will determine what the users can insert. I want to know if this is a good solution. Also, should I expect any significant performance hits?

Some background info:
Oracle version: 7.3+ (up to the current version) Number of records read/updated in one query: anywhere from 0 to 100,000. The average number is around 5,000

Thanks for your help,
Stan Received on Mon Oct 05 1998 - 13:28:41 CDT