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 10:52:30
 
 
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:
00978567
Views:
33
>Hi, Gregory.
>
>>>Well, I though about that, but as it would ruin Rushmore optimization, I'm trying to avoid filters.
>>>
>>>>What about to change this Index. Just add a Filter for .NOT. DELETED() in it.
>
>Guess what? Just checking your idea, I discovered that VFP 9 fully optimizes the query using the candidate tag with a !deleted() filter. Of course, VFP 8 optimization is NONE using the same tag and the same select statement.
>
>Another point for Aleksey, I guess!!!
>
>Thanks a lot!

You're welcome. I'm using this since vfp3

Good to hear about vfp9 optimizing with a !deleted() filter. I'll be able to drop some indexes then.
I guess it will only if SET DELETED = ON
Gregory
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform