Postgres Pro
Downloads
Home   >   mailing lists

Re: [ODBC] Connectivity error: Could not convert from the currentlocale to wide characters - Mailing list pgsql-odbc

From Inoue, Hiroshi
Subject Re: [ODBC] Connectivity error: Could not convert from the currentlocale to wide characters
Date
Msg-id 54d7ff7b-f612-0cc3-f6df-fdd6b5da631c@dream.email.ne.jp
Whole thread Raw
In response to Re: [ODBC] Connectivity error: Could not convert from the current locale to wide characters  ("Andrus" <kobruleht2@hot.ee>)
Responses Re: [ODBC] Connectivity error: Could not convert from the current locale to wide characters  ("Andrus" <kobruleht2@hot.ee>)
List pgsql-odbc
Tree view 
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

pgsql-odbc by date:

Previous
From: Matej Mihelič
Date:
Subject: [ODBC] Q: Is there a way to force psqlODBC with enabled UseDeclareFetch tocommit statements and avoid nesting transactions (savepoints)?
Next
From: "Inoue, Hiroshi"
Date:
Subject: [ODBC] Re: A POSSIBLE BUG: The ODBC standard procedure call ("{ CALLfunction(param) }") is disallowed in ReadOnly ODBC mode whereas "SELECT *FROM function(param)" is let through.