dimkraska wrote:

> Hi all,
>
> Pavel Menshchikov helps me to find the solutioin for my problem with
> UPPER function and german collation,
> but I still wonder is there any other solutionb for this problem.
>
> As I've understood Pavel, inline character Firebird functions like
> UPPER, LOWER etc. should be used like "UPPER(COL1 collate DE_DE)='A'",
> because the functions don't know how properly convert characters.
>
> As the result of this problem, I have to locate all such situations in
> our application and fix them.
> Our application has a lot of sources - I have to do huge amount of
> work to locate and fix all problematic situations.
> And the second problem will appear as soon as our application will
> start to work in other countries, we have to change all "collate
> DE_DE" into other collation in all sources for every market.
>
> Could you please give me some advice on this problem?
>
> Maybe there is the way to setup one collation order for all objects in
> database?
>

Until FB2-Alpha2, default collation order (without collation specified) only ASCII characters are uppercased.

One of the changes in FB2-Alpha3 is that these "non-collated" things are uppercased/lowercased accordingly to UNICODE case table.


Adriano