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

Re: For review: Initial support for COLLATE

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: For review: Initial support for COLLATE
Date: 2005-09-08 06:04:34
Message-ID: 20050908060433.GA4045@svana.org (view raw or flat)
Thread:
Lists: pgsql-patches
On Thu, Sep 08, 2005 at 12:04:42AM +0200, Peter Eisentraut wrote:
> Martijn van Oosterhout wrote:
> > Look at the POSIX interface, look at ICU. They both provide collate
> > order *and* date/time formats *and* number formatting. Pretending
> > they're seperate is silly.
> 
> I'm not pretending.  They *are* separate.  That's why you can set them 
> separately.

They're provided by the same library and set using the same interface.
Currently LC_COLLATE is fixed for the database, but LC_TIME and
LC_NUMERIC can vary between queries. For COLLATE support you need to be
able to specify a different LC_COLLATE for different parts of the
query, this provides that. The POSIX interface isn't flexible enough
for that.

To support COLLATE PostgreSQL's locale support needs to be upgraded and
made more flexible. This is not a surprise. Anything that doesn't use
the new interface isn't affected. I'm a little confused where the
problem is.

If you're worried about functions using the COLLATE tag for something
else, well then we won't do that. Each function/operator decides for
itself whether it's meaningful for them or not...
-- 
Martijn van Oosterhout   <kleptog(at)svana(dot)org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

In response to

Responses

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-09-08 07:41:32
Subject: Re: statement logging / extended query protocol issues
Previous:From: Oliver JowettDate: 2005-09-08 01:14:15
Subject: Re: statement logging / extended query protocol issues

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