Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Proper Way To Check For Duplicate Primary Key
Message
From
23/06/2001 17:00:21
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00522709
Message ID:
00522823
Views:
10
>>What is the most efficient way of handling this?
>>Assuming I have a compound PKEY or CANDIDATE
>>should I do a SEEK before modifying a one of
>>the components or is it more efficient to trap
>>for the error?
>>
>>   ...kt
>
>I usually do both. Not sure, it's the right approach (I had several discussions here about this problem), but this is how it works in our system (single tier):
>I have a special textbox class, which checks for uniqueness of the entered value (if it's not unique, User can correct it immediatelly) and our form also has some mechanism to deal with errors on the save stage.
>

Hi Nadya,

My situation is a bit different. I have a merge
application where I need to merge 10K to 100K
records at a time. I'm trying to find out if
anyone has done any benchmarks that indicate
which is actually the most efficient method of
checking for duplicates.

   ...kt
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform