implementing row level security

[Quoted] i've read through the Finnigan, Kyte, OTN articles, and various threads on the ng. what i didn't find is a description (or assertion) that RLS is a simpler alternative to modifying an existing application code base for filtering table data.

the case i have is like this:

create table orders (order_num number, owner number, lots_data

                            varchar2 (500) )

create table personnel (user_id number, super_id number, more_data
                            varchar2 (500) )

a user should be able to see up the hierarchy, but only the individuals, not their orders (or any other related table data). down the hierarchy, individuals and their orders (and any other related table data). the issue is with filtering on the related tables; i think.

there are about 6 to 10 related data tables. far as i can tell, just the one hierarchy table.

the advantages to the RLS strategy: can be dropped in to any of our client installations; protects the data from out of application access. possible disadvantages: coding is actually more complicated than moding our application.

i'm not looking for code (although i wouldn't say no), rather a "yes you can do this" using RLS and it is easy as pie (or pah as they say down south).

thanks,
robert Received on Thu Apr 29 2004 - 17:15:02 CEST