Re: Oracle's Virtual Private Database functionality

On Wed, Mar 09, 2005 at 13:52:28 -0500,
  Doug Bloebaum <DBloebau@luxotticaRetail.com> wrote:
>
> It's apparent why: the view determines which table it's going to use at
> view creation time, not at query time, so this method is no good.
>
> Is there a "right way" to accomplish what I'm trying to do?

I think the normal way is to have the base tables have an extra attribute
column, an extra table mapping users (or something about the current
session) to attributes and a view for each base table combining the
base table with user to attribute table so that only appropiate rows
show up. If these need to be updatable, you will need to use rules on
the views.