Skip site navigation (1) Skip section navigation (2)

Re: Client encoding win866.

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Попов Михаил Юрьевич <Mihail(dot)Popov(at)galaktika(dot)by>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Client encoding win866.
Date: 2011-06-08 13:49:41
Message-ID: 4DEF7DF5.6010505@tpf.co.jp (view raw or flat)
Thread:
Lists: 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,"set client_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



In response to

Responses

pgsql-odbc by date

Next:From: Fred ParkinsonDate: 2011-06-08 17:04:26
Subject: Re: Logging attempt to connect with odbc
Previous:From: Попов Михаил ЮрьевичDate: 2011-06-08 11:52:46
Subject: Re: Client encoding win866.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group