Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!elroy!mahendo!wlbr!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.databases
Subject: Re: dBase question
Summary: Maybe SCAN isn't what you need
Message-ID: <51@dbase.UUCP>
Date: 14 Apr 89 18:20:29 GMT
References: <6666@bsu-cs.bsu.edu> <1325@naucse.UUCP> <22879@agate.BERKELEY.EDU> <50@dbase.UUCP>
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 19


This discussion, talking about the dBASE construct:

	SEEK <value>
	DO WHILE <key> = <value>
		<process>
		SKIP
	ENDDO

took a strange turn recently when I interjected the dBASE IV SCAN command.
My apologies.  SCAN makes a pass through the entire database, and it would
only be appropriate in extremely low selectivity situations (i.e., if most
of the keys in the index were equal to <value>).  I guess I jumped at an
opportunity to plug one of our new commands.

(Thanks to hjb for pointing this out--I can't email a reply to the address
you sent, BTW.)

/alastair/