From: | Kim Mortensen <kimfmx(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | Hiroshi Saito <hiroshi(at)winpg(dot)jp>, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: problem connecting via ODBC when unicode (now in correct forum.). |
Date: | 2011-01-21 21:28:43 |
Message-ID: | AANLkTi=___v-bo-UHZtg5=6xPwEeMXJx3y+ZC6SzTOVD@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
But the connector is configures individually and I specify the encoding by
the configuration string sat in the JDBC driver. this string sets the
encoding, but apparently it does not work.
BEst Regards
Kim Mortesnen
2011/1/21 Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
> On 01/21/2011 12:35 PM, Kim Mortensen wrote:
>
>> Adrian,
>>
>> Tje letters you are typing are from Danish, but any will do.
>>
>> Now im working abit from memory, but when the databse is build, initdb
>> is using UNICODE as encoding, "C" for locale, so it should be
>> independant of the locale settings.
>>
>
> I believe the problem, as Hiroshi Saito pointed out, is that the client
> encoding is being set on Windows before the connection is attempted and that
> it is picking the wrong one. Per his post pgAdmin and JDBC are probably just
> starting with UTF8 and that is why they succeed. At this point I don't know
> how to get around that.
>
>
>> Best Regards
>> Kim Mortensen
>>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2011-01-21 21:36:47 | Re: problem connecting via ODBC when unicode (now in correct forum.). |
Previous Message | Adrian Klaver | 2011-01-21 21:13:28 | Re: problem connecting via ODBC when unicode (now in correct forum.). |