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



On 15 Nov 2012 06:33, rob@xxxxxxxxx wrote:
Regarding your issue with querying against select/omit logical files
acting differently now that you are on 7.1...

I tried to find that recent post but I can't seem to find it.

<<SNIP>>

On 11/14/2012 05:47 PM Gerald Kern wrote:

Originally posted this morning on RPG-L and per Rob's suggestion
cross posted here now as he indicated this was recently covered
here.

A link to the "recent" thread of the discussion talking about something similar:

_i Query Optimizer selection incorrect access path i_
Robert Clay Date: Mon, 05 Nov 2012 14:25:15 -0500
http://archive.midrange.com/midrange-l/201211/threads.html#00117

To the message originally posted on the RPG400-l, I noted that "I had thought that the CQE was still mandated in 6.1 for all queries whereby a DDS LF has been specified on the FROM clause, irrespective of the IGNORE_DERIVED_INDEX settings." and inquired if perhaps someone knows that is untrue or no longer true with IBM i 7.1 DB2 SQL.
http://archive.midrange.com/rpg400-l/201211/msg00199.html
The DeveloperWorks article referenced by Luis does note that the DDS LF restriction remains on v6r1, but there is no mention of v7r1. Note: A SQL INDEX, _derived_ key or not, can not be specified\named on a FROM clause of a SQL SELECT.
http://www.ibm.com/developerworks/data/library/techarticle/dm-1001maxsqewithdds/index.html


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.