Re: problem connecting via ODBC when unicode (now in correct forum.).
От | Kim Mortensen |
---|---|
Тема | Re: problem connecting via ODBC when unicode (now in correct forum.). |
Дата | |
Msg-id | AANLkTi=___v-bo-UHZtg5=6xPwEeMXJx3y+ZC6SzTOVD@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: problem connecting via ODBC when unicode (now in correct forum.). (Adrian Klaver <adrian.klaver@gmail.com>) |
Ответы |
Re: problem connecting via ODBC when unicode (now in correct
forum.).
|
Список | 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
BEst Regards
Kim Mortesnen
2011/1/21 Adrian Klaver <adrian.klaver@gmail.com>
On 01/21/2011 12:35 PM, Kim Mortensen wrote: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.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.
Best Regards
Kim Mortensen
--
В списке pgsql-odbc по дате отправления: