Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

> "Magnus Hagander" <[email protected]> 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?

No. I think C is the only working locale.
--
Tatsuo Ishii

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match