On Jun 12, 6:52 pm, sybra..._at_hccnet.nl wrote:
> On Tue, 12 Jun 2007 19:37:47 -0000, Valentin Minzatu
>
> <valentinminz..._at_yahoo.com> wrote:
> >I never did an impact analysis between implementing dynamic SQL and
> >VPD and I do not know neither the business case nor the usage/size/etc
> >of the database hence the question (as opposed to affirmation), but
> >from the example it looks like it may be the case for it or for
> >implementing something along those lines.
>
> VPD is always in use, even during export. It is only disabled when SYS
> exports the database.
> Still think this is a viable suggestion to avoid dynamic sql?
>
> --
> Sybrand Bakker
> Senior Oracle DBA
Sybrand, I am not proposing VPD as an alternative to dynamic SQL. Each
of them has its use and the decision has to be made based on the
requirements. One of the arguments in favor of VPD may be, for
example, that the same data access rules apply to export (i.e. if the
user can only access certain subsets through the application, then it
should only be allowed to export the very same ones) - again, this is
just speculation in lack of more details. It may also be the case
where a simple solution such as implementing a view like SELECT * FROM
<table> WHERE <some_field> = SYS_CONTEXT(<namespace>, <parameter>)
would suffice...
Received on Wed Jun 13 2007 - 10:26:13 CDT
