×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




All the recommendations on read triggers is to 'not use them' it's very
expensive processing so I am not willing to go that direction.

-----Original Message-----
From: Scott Mildenberger [mailto:Smildenber@Washcorp.com]
Sent: Friday, October 04, 2002 6:27 AM
To: 'security400@midrange.com'
Subject: RE: [Security400] Row level security

Although I haven't used them myself, would this be a place to use the
new
(V5R1?) read triggers.

Scott Mildenberger

> -----Original Message-----
> From: Andrew Lutz [mailto:andrew.lutz@pmigroup.com]
> Sent: Thursday, October 03, 2002 3:54 PM
> To: security400@midrange.com
> Subject: [Security400] Row level security
>
>
> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> I have a database that has company as an attribute
>
>
>
> This is what we want to do
>
>
>
> *         One database
>
> *         Most users (Companies) cannot view each others information
>
> *         Select users can view the entire database
>
> *         Access to the files happens via all available
> interfaces (i.e.
> not just green screen)
>
>
>
>
>
_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400)
mailing list
To post a message email: Security400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/security400
or email: Security400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.