optimization via selection sets/indices

[Robert Haussmann]

 [...]

> > > Index scan is not available for selection sets
> > containing an "OR".
> > > 
> > 
> > Interesting (and of course logical).  But we tried
> > removing the "or"
> > clause, and *report still counts through all of the
> > records.  If it
> > is truly using the index, it should only hit those
> > records that
> > are relevant (or, say only those records that fit
> > the criteria from
> > the first index applied), right?  Every combination
> > we try goes
> > through the whole file.  
> > 
> > Bob
> > 
> 
> I know you already have a solution here, but have you
> tried removing the selector sentence and the group
> column as well?  If you do this and specify the -j on
> the command line it should use index scan.  Using
> lookup - in -v processing is great - I have used that
> often, but for quick and dirty nothing beats index
> scan.
> 

If we remove the selector sentence and group designators
(and eliminate the "OR" criteria that were e, f, and
g), then it does seem to select via index only.

Bob