Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Lesser records to retrieve - longer time?
Message
 
 
À
25/06/2006 09:42:08
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 SP1
OS:
Windows XP
Database:
Visual FoxPro
Divers
Thread ID:
01130252
Message ID:
01131526
Vues:
24
>>Hi Fabio,
>>
>>>>>What SYS(3054) said about this SELECT?
>>>>Joining intermediate result and table employee_queue_schedules (Cartesian product)
>>
>>>add
>>>
>>>index ON cTrans_Employees_Queues_fk  IN Employee_Queue_Schedules
>>>
>>I watched vfp creating a temp index often in similar situations where that was helpful, which usually is reflected in the sys(3054)-output. Have you found constellations where this is not the case ? If so, any special pattern to watch out for ?
>>
>>regards
>>
>>thomas
>
>Hi Thomas,
>normally VFP create this temp index.
>
>I remember to have seen cases where VFP uses a Cartesian product with an outer join;
>
>I cannot say because this is not true for the Naomi's select, but it can to be one of these.
>
>The uses of char pk and fk doesn't help because it open many setting conditions
>( codepages, collation, set ansi ... ) and then more bugs can to be present;
>I use integer pk only on local table or cursor.
>
>regards
>
>Fabio

The results are really strange, since we have indexes on all FK/PK. We're using GUID for our PKs. AFAIK all indexes are created with MACHINE collate.
If it's not broken, fix it until it is.


My Blog
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform