Re: Row level secrity

From: Steve Butler <sbut-is_at_seatimes.com>
Date: 1995/06/22
Message-ID: <Pine.SUN.3.91.950622145202.15666B-100000_at_seatimes>#1/1


On 20 Jun 1995, 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.

Views with the CHECK= option will work also (including the SELECT). Use a synonym for each user that points to the applicable view for them.

+----------------------------------------------------+
| Steve Butler          Voice:  206-464-2998         |
| The Seattle Times       Fax:  206-382-8898         |
| PO Box 70          Internet:  sbut-is_at_seatimes.com |
| Seattle, WA 98111    Packet:  KG7JE_at_N6EQZ.WA       |
+----------------------------------------------------+
All standard and non-standard disclaimers apply. All other sources are annonymous. Received on Thu Jun 22 1995 - 00:00:00 CEST

Original text of this message