Re: Patch for collation using ICU

From: "John Hansen" <john(at)geeknet(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Palle Girgensohn" <girgen(at)pingpong(dot)net>
Cc: "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <alvherre(at)dcc(dot)uchile(dot)cl>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for collation using ICU
Date: 2005-05-08 23:43:00
Message-ID: 5066E5A966339E42AA04BA10BA706AE50A9314@rodrick.geeknet.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Sent: Monday, May 09, 2005 2:47 AM
> To: Palle Girgensohn
> Cc: Tatsuo Ishii; John Hansen; alvherre(at)dcc(dot)uchile(dot)cl;
> pgman(at)candle(dot)pha(dot)pa(dot)us; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> Palle Girgensohn <girgen(at)pingpong(dot)net> writes:
> >> I'm confused. I thought the ICU patches is intended for using on
> >> broken locale platforms?
>
> > It will sort correctly in *one* locale, using ICU. You still cannot
> > mix different locales in the same database cluster, the collation
> > locale is still fixed at initdb time, unfortunately.
>
> I thought the point of using ICU was to be able to dig out
> from under that restriction? It's a bit of a large pill to
> swallow if we will still have to throw it away someday to
> become SQL spec compliant.

That is not a limitation of ICU but of postgresql.
I don't know what the specs say, but imagine something like:
SELECT foo FROM bar ORDER BY foo WITH LOCALE 'en_US', foobar WITH LOCALE
'jp_JP';

Which would be less difficult to implement using ICU.

>
> regards, tom lane
>
>

... John

Browse pgsql-hackers by date

  From Date Subject
Next Message Satoshi Nagayasu 2005-05-09 00:02:07 Re: [HACKERS] read-only database
Previous Message John Hansen 2005-05-08 23:37:57 Re: Patch for collation using ICU