Re: Row level secrity

In article <3s7d0k$iuk_at_inet-nntp-gw-1.us.oracle.com>, surman_at_oracle.com says...
>
>In article <3s5c6s$m07_at_antares.en.com>, whitney_at_en.com (Nancy C. Whitney) writes:
>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 work nicely, too. You can write a view so that it won't allow an insert that it couldn't re-select and so-forth.

---
Tom Myers Email: t-myers_at_nwu.edu Data Administrator, Attorneys' Liability Assurance Society, Inc. Computer Studies Lecturer, University College, Northwestern University Received on Wed Jun 21 1995 - 00:00:00 CEST