Re: Censoring SQL access -- ideas?

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Stored Procedures, Triggers, and User-Defined Functions on DB2
Universal Database for iSeries Redbook
http://www.redbooks.ibm.com/abstracts/sg246503.html?Open

Depends on your table structure and the logic required to determine if
a user can access the row...

Consider:
create view myview
 as select * from mytable
      where salesrep  = USER
           or salesrep in (select salesrep from table ( ManagedBy(USER)));

or use it in a join
create view myview
 as select *
      from mytable A join table (AuthorizedToAccounts(USER)) B
               on A.acctname = b.acctName;

They've been around since v5r2.

HTH,
Charles


On Wed, Mar 16, 2011 at 2:30 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:
> rob@xxxxxxxxx wrote:
> > Just to toss out an acronym, what about a UDTF?
>
> User-Defined Table Function.
>
> Fascinating.
>
> Found an article on them. By Scott Klement, no less (Hi, Scott!)
>
> Fascinating.
>
> Any specific places (besides Scott's article) I should look for
> information on them? Any opinions on applicability to the problem at hand?
>
> At what OS release did they become available?
>
> --
> JHHL
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.