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

Correction! SQL can use Indexes with WHERE Conditions ... but the Syntax in
the Index WHERE Conditions and the SQL Statement WHERE conditions must be an
exact match.
The easiest way to avoid syntactical problems is , to create a view with all
columns and exactly the same WHERE conditions as in the CREATE INDEX
statement ... then access the data through this view.
... all other dependent (future) views then can be created on the top of the
view with the WHERE conditions.

Keep in mind: Contrary to SQL Indexes or DDS described logical files, a view
does not have a key (it is just a stored SELECT Statement), so there will be
no performance decrease when inserting or updating rows in the base table.
In this way you can really have thousands of views on the same table without
performance decrease ... the hardest thing would be to (re)find the
appropriate view.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Frank
Sent: Sonntag, 21. November 2021 03:38
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Index advisor

As I recall Reeve SQL does not use indexes that have select/omit criteria.
So I would suggest create the indexes without any selection.


On 20/11/2021 5:12 pm, Reeve wrote:
I'm reviewing the suggestions provided by the Index Advisor and some
of the key fields suggested are often blank or zero. Assuming blanks
or zeros aren't valid index entries, should I create my indexes with
WHERE clauses and exclude zeros/blanks?


This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate link:

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2023 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.