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



Regarding Birgitta's comment about native I/O using SQE - I don't believe that is the case - both SQL and RPG make requests to the underlying DB components, so far as I remember conversations I've had. I mean, if SQE were used, there would not be the issue with FIELDPROC and encryption over key fields.

On 1/17/2017 1:48 PM, Nathan Andelin wrote:
-snip-
BTW beginning with release 7.2. all data access including QUERY/400,
OPNQRYF, native I/O is executed with the SQL Query Engine.

In regards to QUERY/400 and OPNQRYF using the SQE, that's progress. I
remember the announcement.

In regards to native I/O using SQE, I'm not sure what you're referring to.
This is not what I'm sure about either - I would need to see the announcement - the one I remember is that at 7.2 all QUERY requests were using SQE.
Note that Vern's point, and my point pertain to PF and Indexes being
essentially identical. SQL Views and Materialized Query Tables obviously
don't have precise counterparts under DDS.
Just a side comment - PF and tables are the equivalents I mentioned - the same MI object type code of x1901, as I recall.

Views and indexes are implemented as LFs - I've not done the DMPOBJ to find the MI object type.

All of these are children of lower-level space objects - gotta love the object-based nature of this our favorite system!

Cheers
Vern

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.