Re: [ODBC] Connectivity error: Could not convert from the currentlocale to wide characters

Поиск
Список
Период
Сортировка
От Inoue, Hiroshi
Тема Re: [ODBC] Connectivity error: Could not convert from the currentlocale to wide characters
Дата
Msg-id 54d7ff7b-f612-0cc3-f6df-fdd6b5da631c@dream.email.ne.jp
обсуждение исходный текст
Ответ на Re: [ODBC] Connectivity error: Could not convert from the current locale to wide characters  ("Andrus" <kobruleht2@hot.ee>)
Ответы Re: [ODBC] Connectivity error: Could not convert from the current locale to wide characters
Список 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


В списке pgsql-odbc по дате отправления:

Предыдущее
От: Matej Mihelič
Дата:
Сообщение: [ODBC] Q: Is there a way to force psqlODBC with enabled UseDeclareFetch tocommit statements and avoid nesting transactions (savepoints)?
Следующее
От: "Inoue, Hiroshi"
Дата:
Сообщение: [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.