>>>>> "AKL" == Anatoly K Lasareff <[EMAIL PROTECTED]> writes:
AKL> The problem is: when database encoding and client encoding are
AKL> different then 'locale' features, such as 'upper' etc don't work. When these
AKL> two encodings are equal - all is OK.
I have partyally win this feature with this 'magic' way. I configure,
make, install and initdb under locale, correspondings to database
encoding. If I wont ALT encoding I use ru_RU.CP866 locale. Then all
'locale' featureas are working. But this is some strange way.
Probably there is nicer method?
--
Anatoly K. Lasareff Email: [EMAIL PROTECTED]
http://tolikus.hq.aaanet.ru:8080 Phone: (8632)-710071
