Re: Design pattern for row-level security?

["Tom Jedrzejewicz @ San Pedro" <TJedrzejewicz@xxxxxxxxxxxx>]

>> Has anyone implemented a system that supports row-level security? 
<< ..snip>>
>> Any experience or places to look for decent design patterns?

I have seen an application called HRizon that has an interesting way to deal 
with this kind of security.  It is not exactly what you want, but it is close.

Basically, you maintain a security table, which has the user and the various 
fields that you want to do row level security against.  Then you do your actual 
operations against a JOIN of the file to be secured and the security file.

Simple example --

SECURITY file
  User
  Authorized Sales Rep
  Sales Rep Update?
  Authorized Item Class
  Item Class Update?

CUSTOMER file
  Customer#
  . . . various other fields
  Sales Rep

ITEM file
  User
  . . . fields
  Item Class

For Customer Inquiry , use a JOIN of CUSTOMER to SECURITY.  For update, use a 
JOIN of CUSTOMER to SECURITY where Sales Rep Update? = Yes.

Take care.

THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.