| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | "M(dot) Bastin" <marcbastin(at)mindspring(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: ORDER BY and Unicode |
| Date: | 2004-05-12 16:38:46 |
| Message-ID: | 26050.1084379926@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> IIRC, right now upper and lower only work correctly in
> single byte encodings. I think when full sql collation
> and character set behavior is done this problem will
> go away.
That unfortunately isn't looking like something that will happen soon.
What might be more practical to do in the short run is to make use of
libc's <wctype.h> routines to do upper/lower case conversion, rather
than <ctype.h>. On machines that have mbstowcs() and wcstombs() I think
this might be fairly straightforward, but I don't have the time or
background to code it up and test it. Any volunteers out there?
Note that this would amount to assuming that LC_CTYPE matches the
database encoding, but the truth of the matter is that the existing
code fails if that's not true anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M. Bastin | 2004-05-12 16:49:45 | Re: ORDER BY and Unicode |
| Previous Message | joseph speigle | 2004-05-12 16:34:56 | Re: ayuda |