optimization via selection sets/indices

[Jeff Harrison]

--- Robert Haussmann <haussma at nextdimension.net>
wrote:

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

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.

Jeff Harrison
jeffaharrison at yahoo.com

---------------------------------------------------------
Author of JHImport and JHExport.  The fastest and
easiest
way to create code for filePro Imports and
Exports.
---------------------------------------------------------







		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail