| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "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: UNICODE/UTF-8 on win32 |
| Date: | 2005-01-02 17:45:33 |
| Message-ID: | 11072.1104687933@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> I didn't consider the C locale. Do you know for a fact that it works
> there on win32 as well, or is that an assumption?
It should work. The only use of strcoll() in the backend is in
varstr_cmp which uses strncmp() instead for C locale. Lack of
working upper/lower is hardly a fatal objection, considering that
we never had that for UTF8 before 8.0 anyway. But you do have to
have working varstr_cmp.
> It would be good to have some way of detecting if it worked or not at
> the time of creation of the database. But I have no idea on how to do
> that in a reasonable way.
At this point I'd say that any combination of UTF8 encoding with a non
C/POSIX locale probably isn't going to work on Windows. Tatsuo, do you
know of other cases that will work?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2005-01-02 18:36:38 | Re: PostgreSQL 8.0.0 Release Candidate 3 |
| Previous Message | Marc G. Fournier | 2005-01-02 14:56:09 | PostgreSQL 8.0.0 Release Candidate 3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2005-01-03 00:48:02 | Re: UNICODE/UTF-8 on win32 |
| Previous Message | Magnus Hagander | 2005-01-02 13:27:54 | Re: UNICODE/UTF-8 on win32 |