> If I created db via SQLcmd CREATE DATABASE aopk WITH encoding = 'LATIN2',
> then databese is created with encoding LATIN2, but if databese is with
> encoding other than SQL_ASCII, than I can't use SET CLIENT_ENCODING =
> 'WINDOWS1250'. I get error ERROR: Conversion between windows1250 and
> LATIN2 is not supported. When database has def. encoding SQL_ASCII, I can
> use cmd SET CLIENT_ENCODING. Why?
That's because some of encoding conversions have not been implemented
yet. Please wait till the beta freeze.
--
Tatsuo Ishii