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:57
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
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:
00978568
Vues:
29
>>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.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform