CollationAttribute messed up handling german umlaute
Bart Pietercil
bart.pietercil at cognosis.be
Tue Oct 7 05:06:28 CDT 2008
Hi Tiemo,
welcome to the list.
I think you are mixing settings
look in the wiki at this page
<http://www.valentina-db.com/dokuwiki/doku.php?id=paradigma:public:en:documentation:vkernel:locale:locale&s=collation
>
it says:
The most intresting for developer is attribute kStrength. Exists the
following values for this attribute:
kPrimary = 0 - ignore accents and case
kSecondary = 1 - ignore case but differ accents
kTertiary = 2 - differ case and accents
to me this says that you would need to use kSecondary (ignoring case
but differ on accents)
hth
Bart
On 07 Oct 2008, at 11:59, Tiemo Hollmann TB wrote:
> 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