home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!comm.mgmt.purdue.edu!landers.mgmt.purdue.edu!landers
- From: landers@comm.mgmt.purdue.edu (Chris Landers)
- Subject: Re: Clipper...Set Unique On/Off
- Sender: news@comm.mgmt.purdue.edu (News owner)
- Message-ID: <landers.131.724601024@comm.mgmt.purdue.edu>
- Date: Thu, 17 Dec 1992 14:03:44 GMT
- Lines: 34
- References: <18587@mindlink.bc.ca>
- Organization: Krannert Graduate School of Management, Purdue University
-
- In article <18587@mindlink.bc.ca> John_Carson@mindlink.bc.ca (John Carson) writes:
- >
- >It has come to my attention on a client program that SET UNIQUE ON/OFF can be
- >the start of corrupted index files.
-
- Yes, this can cause problems if you're not aware of it.....
-
- >I assume that if you SET UNIQUE once with
- >the database you must all the time. If at some location in the .PRG'S it
- >isn't....trouble begins.
-
- Your assumption is wrong.
- Any index created or reindexed with SET UNIQUE ON will be a UNIQUE index,
- that is, only the first occurance of the key will be included in the index
- making the database appear as if it has no duplicate records.
-
- Once an index has been created UNIQUE, it is always UNIQUE, regardless of
- the status of SET UNIQUE. My advice is to SET UNIQUE ON just before
- creating or reindexing an index you want UNIQUE, then set it OFF immediately
- after.
-
- >Has anyone else had this problem?
- >
- >What pseudo code do you suggest do to solve duplicate records without using
- >this SET UNIQUE ON/OFF.
- >
-
- Sorry, I don't have any handy.
-
- <================================><=================================>
- || Christopher Landers || Purdue University - KRAN 708 ||
- || Krannert Computing Center || West Lafayette, IN 47907 ||
- <=================== landers@comm.mgmt.purdue.edu ==================>
-
-