Re: [Firebird-devel] Case-insensitive collations

[James K. L. <jkl...@sc...>]

On Thu, 24 Jun 2004 <ib...@th...> wrote:
> They will search with both ascii/non ascii, what we wish is that these
> words Jo=E3o
> Joao
> JOAO
> JO=C3O
> jO=E3o
> jo=C3o
> etc.
...
> But if the user type
> "JOAO" the data should be stored as "JOAO", when he search for "Jo=E3o"=
=20
> the record should be returned, but as typed (without the accent and=20
> upper case). The users should type it correctly.

This is at least partly a function of the application. =20

It's standard practice to use UPPER() to defeat case-sensitive searches. =
=20

Perhaps a similar function "NOACCENT()", is needed for accents?  I'm not
familiar with languages whose accented characters are sometimes not=20
considered distinct.  (In Swedish, for example, 'a', and '=E5' are two ve=
ry
different letters.)  How is this solved by other implementations? =20

It seems to me the problem with using collations that don't distinguish,
say, between accented and non-accented characters is that the application=
s
are then prevented from distinguishing, every time.  Language contructs
that allow per-use overrides are more flexible. =20

--jkl