Re: Restricting access to data only from certain views -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Restricting access to data only from certain views
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Fri, 24 Sep 2021 19:54:58 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 9/24/21 1:21 PM, Rob Berendt wrote:

Let's say you have a table called TABLEX in schema PF and a view
called VIEWX in schema LF. Can you set it up so that the person can
only see the data in TABLEX by using the view VIEWX? I do not want to
use any exit points if I can avoid it. I prefer to secure the data
and not play whack-a-mole trying to figure out ways to get to the
data.

What about using Row Column Access Controls?

I've never used them myself, but have sat in on COMMON sessions about
them ... it sounds like this is exactly what they are designed for.

david

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.