Re: Row level secrity

surman_at_oracle.com (Scott Urman) wrote:

>In article <3s5c6s$m07_at_antares.en.com>, whitney_at_en.com (Nancy C. Whitney) writes:
>|>
>|>
>|> I would like to achieve row-level security on a per-user basis. I got a
>|> quote for Trusted Oracle, but at $60,000 (for our site with the number of
>|> user we have according to a sales rep at Oracle :-( ) I decided to see
>|> what others are doing. Any ideas?
 

>Probably triggers would be your best bet. This can only be done for insert, update, and delete statements, though, and not select stmts. Check the value
>of the SQL function 'user', and if you don't like it, raise an application
>error.

Another little kludge is to create a separate view of the real table for each user with each user only being able to see their rows. If the WITH CHECK OPTION is used, these users should only be able to create rows in this table that they would be able to see.

John Fruetel
jfruetel_at_ainet.com Received on Sun Jun 25 1995 - 00:00:00 CEST