| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "John Hansen" <john(at)geeknet(dot)com(dot)au>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <pgsql-hackers-win32(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 |
| Date: | 2005-02-25 00:45:54 |
| Message-ID: | 5066E5A966339E42AA04BA10BA706AE5625B@rodrick.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
> currently, upper/lower does not work with 2+ byte unicode
> characters, on any OS under the C locale.
Btw,...
There are only 15 cases in the utf8 repertoire that depends on locale, these are the only cases where pg should report:
ERROR: invalid multibyte character for locale
HINT: The server's LC_CTYPE locale is probably incompatible with the database encoding.
When doing a select upper/lower (col)
All others should work just fine.
The error should probably also be changed to a warning, and just return the offending character unmodified.
... John
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-02-25 01:11:43 | Re: Finding if old transactions are running... |
| Previous Message | John Hansen | 2005-02-25 00:29:32 | Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-02-25 03:05:57 | Re: [pgsql-hackers-win32] Repleacement for src/port/snprintf.c |
| Previous Message | John Hansen | 2005-02-25 00:29:32 | Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 |