Re: Client encoding win866. - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: Client encoding win866.
Date
Msg-id 4DEF7DF5.6010505@tpf.co.jp
Whole thread Raw
In response to Re: Client encoding win866.  (Попов Михаил Юрьевич <Mihail.Popov@galaktika.by>)
Responses Re: Client encoding win866.
List pgsql-odbc
(2011/06/08 20:52), Попов Михаил Юрьевич wrote:
>
>>> Hi.
>>>
>>> Can you please tell me how to change client encoding in ODBC?
>>>
>>> I tried after a connection to execute SQLExecDirect (stmthp, "set
>>> client_encoding to \" WIN866 \ ";", SQL_NTS) , but the encoding is still
>>> a win1251.
>
>> How do you confirm the client_encoding?
>
> Few details...
> I create connection and before all the bindings of parameters and columns, and before SQLPrepare I do
SQLExecDirect(stmthp,"setclient_encoding to \"WIN866\";",SQL_NTS); 
> Then after SQLPrepare, SQLBindParameter and after SQLExecute I get an error:
> Error code 22P05 with message ERROR: character 0x83 of encoding "WIN1251" has no equivalent in "MULE_INTERNAL";
>
> In this example, the function I pass the 'select * from "Table"'

What will happen when you don't call *set client_encoding to ...*?

regards,
Hiroshi Inoue



pgsql-odbc by date:

Previous
From: Попов Михаил Юрьевич
Date:
Subject: Re: Client encoding win866.
Next
From: "Fred Parkinson"
Date:
Subject: Re: Logging attempt to connect with odbc