Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQL SELECT and code pages problem
Message
De
27/07/2001 03:21:51
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
 
À
26/07/2001 12:32:08
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00535512
Message ID:
00536234
Vues:
15
>Thanks, Cetin.
>
>Please, can you be more specific concerning the Title of the discussion
>about SQL strings comparison problems.
>I can't find it.
>
>Really, my problem is about comparing longer strings (not only one character)
>in the SELECT (maybe my example is too simplified for demonstration), but I
>can't use your suggestion with ASC(...).
>
>Pavel Kouril

Pavel,
Check Thread #483532
It doesn't have collating at all and trimming is an issue. However 'set ansi on' vs '==' was a solution. This makes me think if field lengths are different w/o set ansi any string comparison might fail.
Bela, title and original message codepage setting at first made me think of collate sequence as well. I remember I reported a seek() fail and _Tally returning wrong info with collate sequences other than machine years ago. But in original message there is 'set collate to machine' and Pavel says there are no indexes on tables. I think it wouldn't apply in this case (but who knows).

PS:While checking 'collating' documents noticed MS document for correcting documentation is wrong :) They correct supported collating sequences and again TURKISH is not listed. Maybe they're not still aware TURKISH is supported (of course not in any of docs - I had found it with lowlevel check and to my surprise worked) :)

Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform