optimization via selection sets/indices

[Robert Haussmann]

> Robert Haussmann wrote:
> [... "index scan" not working with the following selection set ...]
> > a and b and c and d and (e or f or g)
> > a:9:eq:000575
> > b:2:ge:07/01/2001
> > c:2:le:12/31/2004
> > d:16:eq:P
> > e:3:eq:P
> > f:3:eq:D
> > g:3:eq:TR
> [...]
> 
> 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