Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Avoiding candidate key conflicts in a VFP DBC
Message
From
19/01/2005 11:00:20
 
 
To
19/01/2005 10:52:57
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP1
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
00978227
Message ID:
00978575
Views:
29
Hi, Hilmar.

>>>What about to change this Index. Just add a Filter for .NOT. DELETED() in it.
>>
>>Well, I though about that, but as it would ruin Rushmore optimization, I'm trying to avoid filters.
>
>If you need it for Rushmore Optimization, you can create two indices, on the primary key or alternate primary key: one regular, without a filter, for Rushmore Optimization, and an index marked as "primary" or "candidate", with a filter.

I find out that VFP 9 fully optimizes queries using the candidate tag with a !deleted filter, so the issue is solved (migrating to VFP 9 was already on the plan).

Thanks a lot!
Previous
Reply
Map
View

Click here to load this message in the networking platform