Re: Censoring SQL access -- ideas?

On v6.1 & higher you can create indexes with select/omit logic:

create index qtemp/idx on ttlib/gppfile (wact4)
where substring(account,2,1)='1'

Thanks,
Tommy Holden



From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/16/2011 01:03 PM
Subject: Re: Censoring SQL access -- ideas?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



On 3/16/2011 12:31 PM, Charles Wilt wrote:

On Wed, Mar 16, 2011 at 12:40 PM, James Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:

Charles Wilt wrote:

Also, if you plan for the users to sign on through JDBC with there own
user ID, you could make the tables PUBLIC *EXLCUDE and offer a view
that includes something to the effect of
create view myview
as SELECT col1, col2
from mytable
where SALE_REP = CURRENT_USER;

Fascinating. A view that checks some field against the current user.
Just out of morbid curiosity, is there a DDS Select/Omit equivalent to
the above WHERE clause?

Not that I'm aware of...views are lots more powerful than logical files.

Better for some things, perhaps. But there's no ORDER BY and as of
recent releases they won't even work on legacy data with multiple
formats. So, sure, views are great (I use them all the time) but they
are not a silver bullet replacement for logical files.

Joe