RE: sqlrpgle select statements -- 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.

Subject: RE: sqlrpgle select statements
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Wed, 1 Mar 2006 16:05:20 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

 >> I've run into cases where logicals that exactly matched the where and
order by clauses were not used. 

Run the program in debug or simply key the select into Op-Nav and have it
analyze the SQL.  Just because there is an apparent exact match in a logical
does not necessarily mean that it will be the fastest access route.  The
debug statements in the Job Log will show you _why_ the query optimizer
rejected the path in question.


Jon Paris
Partner400

www.Partner400.com
www.RPGWorld.com 
-----Original Message-----

As an Amazon Associate we earn from qualifying purchases.

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.