> On HPUX 10.20, mbstowcs seems to treat all byte values as
> single-byte characters in C locale, so my sample-of-one says
> that it works everywhere ;-).

Right, so for the sample SQL I sent earlier, the result would be the same as the input?
That's hardly a working upper/lower....

If a character doesn't have case then fine, but one that does, should at least produce a warning if it cannot be converted.


.... John

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

"John Hansen" <john@geeknet.com.au> writes:
> Right, so for the sample SQL I sent earlier, the result would be the same as the input?
> That's hardly a working upper/lower....

[ shrug... ] It works per the locale definition, which is that only
7-bit-ASCII a-z/A-Z get converted.

The bottom line here is that we rely on the locale setting for this
behavior, and that's not likely to change real soon. If you dislike
the locale definition then you should be using a different locale.
In particular I think the issue here is really that your platform's
definition of "C locale" says that bytes above x7F are illegal
characters. My platform's doesn't. The thing to be changing is the
locale definition.

regards, tom lane

---------------------------(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