Re: BUG #4319: lower()/upper() does not know about UNICODE case mapping - Mailing list pgsql-bugs

On Jul 25, 10:17=A0am, Zdenek.Kot...@Sun.COM (Zdenek Kotala) wrote:
> Valentine Gogichashvili napsal(a):
>
> > Hi,
>
> Hi
>
> > I understand, that it is more a feature, but it does not help me anyway=
s...
>
> > On the UNICODE databases lower and upper functions are using system loc=
ale
> > settings (that cannot be changed after initializing DB?) and does not k=
now
> > anything about UNICODE case mapping.
>
> > The problem really becomes 'a problem' on multilingual systems. I have =
to
> > store data for German, Russian and Romanian languages together. =A0
>
> I understand you and I hope things will be better. See collation per data=
base
> project:http://wiki.postgresql.org/wiki/Gsoc08-collation
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Zdenek
>
> --
> Zdenek Kotala =A0 =A0 =A0 =A0 =A0 =A0 =A0Sun Microsystems
> Prague, Czech Republic =A0 =A0http://sun.com/postgresql
>
> --
> Sent via pgsql-bugs mailing list (pgsql-b...@postgresql.org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/p=
gsql-bugs

This is actually a high time to include support for different
collates... but do you think it is enough to add the change to the
database or maybe start building the collation support for every text
column actually?