home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!decwrl!pa.dec.com!nntpd2.cxo.dec.com!tincup.enet.dec.com!lindsey
- From: lindsey@tincup.enet.dec.com (Randy Lindsey)
- Newsgroups: comp.databases
- Subject: Re: What is Rushmore indexing - FOXPRO?
- Message-ID: <1992Nov12.001603.529@nntpd2.cxo.dec.com>
- Date: 12 Nov 92 00:06:49 GMT
- Article-I.D.: nntpd2.1992Nov12.001603.529
- References: <74316@hydra.gatech.EDU>
- Sender: usenet@nntpd2.cxo.dec.com (USENET News System)
- Organization: Colorado Software Solutions, Inc.
- Lines: 23
-
-
- In article <74316@hydra.gatech.EDU>, gt2768b@prism.gatech.EDU (JENGLUNG LIN) writes...
- >Can someone tell me what is the indexing method used by FOXPRO -
- >RUSHMORE ?
-
- Rushmore is sort of a "turbo-access" method. Foxpro invokes it automatically
- when the right conditions apply (suitable indexes on the right fields,
- enough memory). I've heard it's some kind of bit-mapping technique.
-
- It is used by the SQL SELECT optimizer and when you use the "FOR" clause
- on various Foxpro commands. So it's a "set of records" thing--it quickly
- retrieves a set of records that match your query, which you can then access
- individually, or browse, or print, etc.
-
- To take advantage of it, you want to have an index on each field that will
- appear in your SELECT WHERE or FOR clause. Some people just completely
- invert their databases--they put an index on (nearly) every field. Using
- compact structural indexes takes a lot of the sting out of that.
-
- Anyone know more about how Rushmore works? I'm curious about the details
- myself.
-
- Randy
-