| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Mahmoud Taghizadeh <m_taghi(at)yahoo(dot)com>, peter_e(at)gmx(dot)net, gsstark(at)mit(dot)edu, db(at)zigo(dot)dhs(dot)org, mail(at)joeconway(dot)com, sszabo(at)megazone(dot)bigpanda(dot)com, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: using strxfrm for having multi locale/please vote for adding this function in contribution |
| Date: | 2005-06-07 02:02:55 |
| Message-ID: | 87oeaij54g.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I think we have concluded that the use of the ICU library is the way we
> are going to accomplish multi-locale support in the future.
You did? It really seemed like there was one crowd pushing ICU and hardly
anyone else interested in piling a huge library dependency on Postgres. It
seemed like ICU was only really necessary if you wanted some esoteric
functionality that wasn't entirely explained.
I'm having no trouble handling multi-locale already using the strxfrm
implementation that was posted and refined by several people on the mailing
list.
Yes it's true that on some OSes it wouldn't be tolerably efficient but on
glibc it's more than tolerable. If better solutions (strxfrm_l) become
available at some point in the future then it would be about as efficient as
it could be on platforms where those features are available.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-06-07 02:11:15 | Re: using strxfrm for having multi locale/please vote for |
| Previous Message | Joe Conway | 2005-06-07 01:24:52 | Re: [SQL] ARRAY() returning NULL instead of ARRAY[] resp. |