Re: _cipher API vs Qc3Encrypt/Qc3DecryptData vs SQL -- RPG400-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.

Hi Rob,

How about doing at least some of that with a view, e.g.

create view qtemp/test as ( select SRCSEQ, SRCDAT, case when user = 'PDOW' then SRCDTA else 'hidden' end SRCDT
from QCLSRC)
Presumably the view could use USER to link to another file that specifies other rules.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

rob@xxxxxxxxx wrote:

A before read trigger would allow us to do things like programmatically decide if the person has access to a particular row in a table. For instance, a vendor application often decides who has access to certain payroll records based on a number of factors, such as job class, or location, or some such thing. A before read trigger would allow us to lock the barn with that same logic instead of just reporting on who stole the horse. Putting a UDF on every field to duplicate that logic, and returning a null or default value is not near as nice. I've done UDF's. Check out the faq.midrange.com.

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.