From: | "Inoue, Hiroshi" <h-inoue(at)dream(dot)email(dot)ne(dot)jp> |
---|---|
To: | arnaud(dot)listes(at)codata(dot)eu |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: BUG: odbc statement_timeout gets set to 30000 |
Date: | 2017-11-17 08:26:25 |
Message-ID: | 2ac1ec8f-6db8-aaea-6bed-f818651b64f6@dream.email.ne.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi,
On 2017/11/17 16:39, Arnaud L. wrote:
> Le 17/11/2017 à 08:34, linuxyeti a écrit :
>> I've found a problem with at least the 906 and 1000 odbc driver, in
>> that, no
>> matter what statement_timeout is set to, after initially connecting and
>> setting the value to that specified in the connection settings, it is
>> then
>> subsequently set to 30000.
>
> I've witnessed it too, and fixed it by setting my ado connection's
> commandtimeout to 0 in my scripts. (oADODBConn.CommandTimeout = 0)
The default value of CommandTimeout property is 30.
>
> But just like you I was surprised by this change, so it might be a bug.
It's because of an enhancement (SQL_QUERY_TIMEOUT option support since
9.5.0400) not a bug.
regards,
Hiroshi Inoue
>
>
> Regards
>
> --
> Arnaud
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Arnaud L. | 2017-11-17 11:15:23 | Re: BUG: odbc statement_timeout gets set to 30000 |
Previous Message | Arnaud L. | 2017-11-17 07:39:58 | Re: BUG: odbc statement_timeout gets set to 30000 |