Postgres Pro
Downloads
Home   >   mailing lists

Re: problem connecting via ODBC when unicode (now in correct forum.). - Mailing list pgsql-odbc

From Kim Mortensen
Subject Re: problem connecting via ODBC when unicode (now in correct forum.).
Date
Msg-id AANLkTinX-Re+QXPhCb8PqatteaTthKnMtitQ2inuhgZh@mail.gmail.com
Whole thread Raw
In response to Re: problem connecting via ODBC when unicode (now in correct forum.).  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: problem connecting via ODBC when unicode (now in correct forum.).  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-odbc
Tree view
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

2011/1/21 Adrian Klaver <adrian.klaver@gmail.com>
On 01/21/2011 10:20 AM, Kim Mortensen wrote:
Thank you for your input,

it may be that only ascii chars is to be used, however it should be
stated or a bug report filled out, as you can insert Login Roles with
different charakterset as you can actually use.

Best Regards
Kim Mortesnen



I cranked up a virtual instance of Windows XP to try to figure this out. Turns out I need  to know more about how encoding works on Windows. I had no problem creating the role æøå on my Linux server and logging in using psql. On Windows not so, I get:

Username [postgres]: æøå
Password for user µ°Õ:
psql: FATAL:  password authentication failed for user "æøå"

and through ODBC:

2011-01-21 12:16:32 PSTFATAL:  password authentication failed for user "æøå"

Seems client encoding is getting in the way somehow, just not sure how.

--

pgsql-odbc by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: problem connecting via ODBC when unicode (now in correct forum.).
Next
From: Adrian Klaver
Date:
Subject: Re: problem connecting via ODBC when unicode (now in correct forum.).