Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!watmath!xenitec!timk
From: timk@xenitec.uucp (Tim Kuehn)
Newsgroups: comp.databases
Subject: Re: Deleting duplicate records
Summary: Not quite!
Keywords: unique key, deleteing duplicate records
Message-ID: <1989Jul19.193836.2424@xenitec.uucp>
Date: 19 Jul 89 19:38:36 GMT
Reply-To: timk@xenitec.UUCP (Tim Kuehn)
Organization: Xenitec Consulting Services, Kitchener, ON
Lines: 28

roger@tcgould.tn.cornell.edu (Roger Boissonnas) writes:
>In article <1989Jul17.165249.26554@xenitec.uucp> timk@egvideo.UUCP (Tim Kuehn) writes:
>>
>>Program:
>>--------


... source code deleted ...
>You can do the same thing in only three lines:
>USE dborig
>INDEX ON <key> TO ndxuniq UNIQUE
>COPY TO dbuniq
>
>
>Roger Boissonnas                              roger@tcgould.tn.cornell.edu
>Cornell Theory Center                                      (607) 255-8306

You know what - you're right! I always thought the copy command used the
entire database, irrespective of index keys. Learn something new every
day I guess....

+-----------------------------------------------------------------------------+
|Timothy D. Kuehn	       timk@egvideo (soon to be timk@xenitec)	      |
|TDK Consulting Services			       !watmath!xenitec!timk  |
|871 Victoria St. North, Suite 217A					      |
|Kitchener, Ontario, Canada N2B 3S4 		       (519)-741-3623 	      |
|DOS/Xenix - SW/HW. uC, uP, DBMS. 		       Satisfaction Gauranteed|
+-----------------------------------------------------------------------------+