Re: Designing for Row Level Security

Hi Abdullah,

There is one more way to go. I can not explain in details how it is done due to Patent issues, but I can tell that my solution handles row level security in a table and supports this.

1. Different users can have Select/Insert/Update/Delete in any combination on any row.
2. There is only ONE view needed on the table. Regardless of number of users.
3. A user can have either direct permission on a table or via one or more roles.
4. Precedence is handled if there is a conflict between different permissions granted on current user on any row.
5. Different permissions can be given current user on different day or time.

EVERYTHING is handled during runtime. This means that the rows are protected both ways. Accessed either by an application or direct via SQL Query tools.

The solution uses only standard db techniques.

Currently the solution is running in approximate 100 installations world wide. It is accepted by US-FDA and HIPAA regulations.

Regards
Anders Received on Wed Jun 11 2003 - 23:28:01 CEST