Re: Connectivity error: Could not convert from the current locale to wide characters

From: "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp>
To: Andrus <kobruleht2(at)hot(dot)ee>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Connectivity error: Could not convert from the current locale to wide characters
Date: 2017-08-25 08:02:49
Message-ID: 54d7ff7b-f612-0cc3-f6df-fdd6b5da631c@dream.email.ne.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hi Andrus,

On 2017/08/25 16:05, Andrus wrote:
> Hi,
>
> Thank you.
>
>> Could you turn on the Debug option in Advanced options (DataSource)
>> page As well?
>
> I looked into all pages 1-3 ion advanced options.
> There is no Debug option in any place in ODBC config.

Oops sorry, it is Mylog option. in page 1 which should be turned on.

>
> Aslo in page 1 (screenshot attached) it looks like driver tries to
> write logs into root directory in c: drive.
> In my knowldedge, this is disabled by default in newer windows OSes.
> I can turn of Windows ODBC tracing and send this log if it helps.

Probably ODBC trace is useless in this case.
ISTM You sent me Mylog with global Mylog option is turned on.
Mylog output with per datasource Mylog option turned on is necessary.

regards,
Hiroshi Inoue

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Inoue, Hiroshi 2017-08-25 08:23:43 Re: A POSSIBLE BUG: The ODBC standard procedure call ("{ CALL function(param) }") is disallowed in ReadOnly ODBC mode whereas "SELECT * FROM function(param)" is let through.
Previous Message Matej Mihelič 2017-08-25 07:45:51 Q: Is there a way to force psqlODBC with enabled UseDeclareFetch to commit statements and avoid nesting transactions (savepoints)?