Re: Design pattern for row-level security? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

You may need to think about referntial integrity options as well as triggers--

Also look at some of the abilities of logical files-- you would have to do some program changing, but you can create an LF that only includes the fields that you want updatable, and maybe access the PF as read only... maybe.

Is this a case where program logic is your best solution?

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx

Has anyone implemented a system that supports row-level security? By
row-level I'm speaking of a system where you could say:

Mike can add comments to items.
Mike can change items.
Mike can NOT access item 12345 in any way (not even read)
Jane can display any item where she is the product-line manager
Jane can not display item 87997 even though she is product-line manager
Pete can edit items where he is buyer
Pete can edit item 99890 (even though he isn't buyer)
Pete can add notes to items where he is seconday buyer, but can't change
them.

Any experience or places to look for decent design patterns?

-Walden

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.