× 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.



Encrypting an indexed field will radically alter its sequence. But if the
idea is just to properly order the rows, it seems like an OAR handler could
decipher the encrypted field and output the table to a temporary User Index
when the file is opened, so that all subsequent reads and chains might be
performed against the properly ordered User Index.



On Fri, Jul 29, 2016 at 10:17 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

IBM wants to get all of us using the SQL capabilities and the SQE engine
so this might be the perfect thing to do that.


I agree that's a presumption implied in the article. But it doesn't really
answer my question of what value SQL I/O added to FIELDPROC encryption. Was
it SQL I/O that solved the problem, or was it supplemental logic in OAR
that solved the problem?




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.