On Jul 25, 10:17 am, Zdenek(dot)Kot(dot)(dot)(dot)(at)Sun(dot)COM (Zdenek Kotala) wrote:
> Valentine Gogichashvili napsal(a):
> > 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
> Zdenek Kotala Sun Microsystems
> Prague, Czech Republic http://sun.com/postgresql
> Sent via pgsql-bugs mailing list (pgsql-b(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-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
In response to
pgsql-bugs by date
|Next:||From: Jeff Galyan||Date: 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 |