Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Avoiding candidate key conflicts in a VFP DBC
Message
De
19/01/2005 10:52:30
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 9
OS:
Windows XP SP1
Network:
Windows 2003 Server
Database:
MS SQL Server
Divers
Thread ID:
00978227
Message ID:
00978567
Vues:
31
>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
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform