| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, PostgreSQL hackers list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unicode upper() bug still present |
| Date: | 2003-10-20 13:05:48 |
| Message-ID: | 1794.1066655148@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
>> It's been suggested that we could use <wctype.h> where available.
>> However there are a bunch of issues that would have to be solved to make
>> that happen. (How do we convert between the database character encoding
>> and the wctype representation?
> How do we do it for sorting ?
We don't --- strcoll() handles it all internally.
> It seems inconsistent that we do use locale-aware sorts but not
> upper/lower.
We do have locale-aware upper/lower ... but only in single-byte
encodings. I think it works for the 7-bit-ASCII subset of multibyte
encodings, too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-20 13:18:54 | Re: Unicode upper() bug still present |
| Previous Message | Robert Treat | 2003-10-20 12:52:20 | Re: [HACKERS] Mapping Oracle types to PostgreSQL types |