| From: | Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org> |
|---|---|
| To: | Tim Allen <tim(at)proximity(dot)com(dot)au> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vague idea for allowing per-column locale |
| Date: | 2001-08-10 11:49:48 |
| Message-ID: | Pine.LNX.4.33.0108101229560.31429-100000@sphinx.mythic-beasts.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 10 Aug 2001, Tim Allen wrote:
> > We have realized that allowing per-column locale would be difficult with
> > the existing C library interface, because setlocale() is a pretty
> > inefficient operation. But I think what we could allow, and what would be
> Yes, the C library locale notion is somewhat broken, or at best limited,
> imho. It doesn't fit at all well with the needs of a server that can have
> clients in different locales, or even clients in the same place who have
> different locale preferences.
This may be of interest:
http://www.cygnus.com/~drepper/tllocale.ps.bz2
It's not clear if glibc implements it yet, nor if people like
the interface, but it seems like a nice, easily-wrapped and
stubbed option, which might come for free on at least one OS.
Matthew.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2001-08-10 12:38:24 | Re: PL/pgSQL bug? |
| Previous Message | Vince Vielhaber | 2001-08-10 10:38:08 | Re: OpenFTS (Open Source Full Text Search engine) pre-announce |