|
On Sep 3, 2018, at 2:12 PM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:
<Birgitta>
may be I'm missing something or did not read all posts, but ... the solution I provided is documented (as well as other pitfalls with their solutions) in the "Row And Column Access Control" Redpaper:
</Birgitta>
The official documentation is the "SQL Reference" and there is not a single word about any problems with Field Procs. The origin of the problems is RLA and it's "native" access (and other "native" interfaces, Query, CPYF and CRTDUPOBJ). For a solid solution. I would have expected, that these interfaces could not corrupt the underlaying architecture and it could not have been so hard to disable RLA access unless the needed constraints are activated.
D*B
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
