Skip site navigation (1) Skip section navigation (2)

Re: BUG #4319: lower()/upper() does not know about UNICODE case mapping

From: valgog <valgog(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4319: lower()/upper() does not know about UNICODE case mapping
Date: 2008-07-25 14:15:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Jul 25, 10:17 am, Zdenek(dot)Kot(dot)(dot)(dot)(at)Sun(dot)COM (Zdenek Kotala) wrote:
> Valentine Gogichashvili napsal(a):
> > Hi,
> Hi
> > I understand, that it is more a feature, but it does not help me anyways...
> > On the UNICODE databases lower and upper functions are using system locale
> > settings (that cannot be changed after initializing DB?) and does not know
> > 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.  
> I understand you and I hope things will be better. See collation per database
> project:
>                 Zdenek
> --
> Zdenek Kotala              Sun Microsystems
> Prague, Czech Republic
> --
> Sent via pgsql-bugs mailing list (pgsql-b(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:

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?

In response to

pgsql-bugs by date

Next:From: Jeff GalyanDate: 2008-07-25 22:00:20
Subject: BUG #4324: Default value for a column is not returned in select when column has not been explicitly set
Previous:From: K, Niranjan (NSN - IN/Bangalore)Date: 2008-07-25 11:54:36
Subject: Re: Psql or test application hangs when interface is down for the DB server

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group