Re: client encoding mismatch

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: Андрей Репко <repko(at)sart(dot)must-ipra(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>, "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>
Subject: Re: client encoding mismatch
Date: 2005-09-22 12:15:34
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC2E1A@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: Андрей Репко [mailto:repko(at)sart(dot)must-ipra(dot)com]
> Sent: 22 September 2005 11:41
> To: Dave Page
> Subject: Re[4]: [ODBC] client encoding mismatch
>
> Hello Dave,
>
> Thursday, September 22, 2005, 1:01:40 PM, Вы писали:
>
>
> The same result :(
> And when I set Advanced Options -> connect set to
> 'conn_encoding="WIN1251"' in log file I see the next:
>
> Global Options: Version='08.01.0005', fetch=100, socket=0,
> unknown_sizes=254, max_varchar_size=8190,
> max_longvarchar_size=20725080
> disable_optimizer=1, ksqo=1, unique_index=1,
> use_declarefetch=0
> text_as_longvarchar=1,
> unknowns_as_longvarchar=0, bools_as_char=1 NAMEDATALEN=64
> extra_systable_prefixes='dd_;',
> conn_settings='' conn_encoding='WIN'
>

Hmm, how odd. It works for me. I assume you are using the ANSI driver?

Hiroshi - can you use win1251 with your patch?

Regards, Dave

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Saito 2005-09-22 12:59:24 Re: client encoding mismatch
Previous Message Dave Page 2005-09-22 09:23:38 Re: ODBC driver types