Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQL Select not optimized with VFP9
Message
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 SP2
Database:
Visual FoxPro
Divers
Thread ID:
00986454
Message ID:
00986460
Vues:
31
Hi Sergey,

Current Codepage = 1252
Sofe301 Codepage = 850
Sofe110 Codepage = 437

Now I remember some discussions about problems with different codepages. Somehow I think that you don't need the index definitions, but know the reason after seeing this codepages right?

/Torgny



>What indexes do you've on those tables? What's tables codepage and current code page?
>
>>
>>This was fully optimized with VFP8:
>>
>>SELECT Distinct Sofe301.prgrupp,;
>>                Sofe301.namn,;
>>                Sofe110.opnr,;
>>                Sofe110.ejbelagg;
>>                FROM sofe110;
>>                INNER JOIN sofe301;
>>                ON  sofe110.prgrupp = Sofe301.prgrupp;
>>                WHERE SUBSTR(Sofe301.artnr,11,8) =  ?vp_artnum  AND;
>>                Sofe110.ejbelagg = 'J' ;
>>                ORDER BY Sofe110.opnr into cursor crsOpnr
>>
>>Using index tag Ejbelagg to rushmore optimize table sofe110
>>Rushmore optimization level for table sofe110: full
>>Using index tag Subartnr to rushmore optimize table sofe301
>>Rushmore optimization level for table sofe301: full
>>Joining table sofe301 and table sofe110 using index tag Opprgr
>>
>>
>>But with VFP9 it is not:
>>
>>Rushmore optimization level for table sofe110: none
>>Rushmore optimization level for table sofe301: none
>>Joining table sofe110 and table sofe301 using temp index
>>
>>
>>Can anyone please tell me the reason for this?
/Torgny
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform