[jira] [Comment Edited] (IGNITE-16608) ODBC: SQL_ATTR_CONNECTION_TIMEOUT does not affect statement execution

["Igor Sapego (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-16608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500476#comment-17500476 ] 

Igor Sapego edited comment on IGNITE-16608 at 3/3/22, 3:33 AM:
---------------------------------------------------------------

Ready for review. [~ivandasch], [~ptupitsyn] can you take a look please?


was (Author: isapego):
Ready for review. [~ivandasch], [~ptupitsyn] take a look please?

> ODBC: SQL_ATTR_CONNECTION_TIMEOUT does not affect statement execution
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-16608
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16608
>             Project: Ignite
>          Issue Type: Bug
>          Components: odbc
>    Affects Versions: 2.12
>            Reporter: Igor Sapego
>            Assignee: Igor Sapego
>            Priority: Major
>             Fix For: 2.13
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> According to [documentation|https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlsetconnectattr-function] SQL_ATTR_CONNECTION_TIMEOUT is described as follows:
> {noformat}
> An SQLUINTEGER value corresponding to the number of seconds to wait for any request on the connection
> to complete before returning to the application. The driver should return SQLSTATE HYT00 (Timeout expired)
> anytime that it is possible to time out in a situation not associated with query execution or login.
> If ValuePtr is equal to 0 (the default), there is no timeout.
> {noformat}
> It means SQL_ATTR_CONNECTION_TIMEOUT should also work for long queries, but currently it does not.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)