> > select upper('æøå');
> > ERROR: invalid multibyte character for locale
> > HINT: The server's LC_CTYPE locale is probably
> incompatible with the database encoding.
>
> > Consequently it seems that is does not work.
>
> "It fails on my machine" should not be read as "it doesn't
> work for anyone".
> It all depends on how your local mbstowcs() works.

Ok,... Do you have an example of a system on which it works?


.... John

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

"John Hansen" <john@geeknet.com.au> writes:
>> "It fails on my machine" should not be read as "it doesn't
>> work for anyone".
>> It all depends on how your local mbstowcs() works.

> Ok,... Do you have an example of a system on which it works?

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 ;-).

Nonetheless, it's clear that in C locale mbstowcs cannot be buying us
anything compared to using the old <ctype.h> macros, so I'm fine with
adding a check on the locale as per previous discussion.

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