AW: CollationAttribute messed up handling german umlaute
Tiemo Hollmann TB
toolbook at kestner.de
Tue Oct 7 05:07:45 CDT 2008
Sorry for my first post - sometimes reading helps :) just when posting the
word"accents" I remembered the docs...
I should have set kStrength not to kPrimary, but "kSecondary".
Thanks anyway
Tiemo
> -----Ursprüngliche Nachricht-----
> Von: valentina-bounces at lists.macserve.net [mailto:valentina-
> bounces at lists.macserve.net] Im Auftrag von Tiemo Hollmann TB
> Gesendet: Dienstag, 7. Oktober 2008 11:59
> An: ValentinaListe
> Betreff: CollationAttribute messed up handling german umlaute
>
> Hello,
>
> I am new to valentina (working with revolution) and this is my first
> posting
> to this list, so I want to say hello to all.
>
> My issue is that I want always Case insensitivness with all SELECT
> statements. So I have set the CollationAttribute of the db kStrength to
> kPrimary. So far so good, selecting upper and lower standard characters
> works fine.
>
> BUT selecting the german umlaute is completely messed up. When searching
> for
> ä the select result brings not only all ä and Ä, but also all a
> and
> A, same with selecting for a brings up a, A, ä, Ä. So the
> german
> umlaute are handled as their equivalent chars without accents.
>
> I am sure (or at least hoping) that some European user has found a
> solution
> for this before, because I am really not an SQL pro.
>
> Thanks for any suggestion
>
> Tiemo
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina
More information about the Valentina
mailing list