[IGNITE-16608] ODBC: SQL_ATTR_CONNECTION_TIMEOUT does not affect statement execution

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.12
• Fix Version/s: 2.13
• Component/s: odbc
• Release Note: Fixed ODBC connection timeouts
• Ignite Flags: Release Notes Required
• Assignee: Igor Sapego
• Reporter: Igor Sapego
• Created: 21/Feb/22 18:24
• Updated: 13/May/22 13:07
• Resolved: 05/Mar/22 10:57

Description

According to documentation SQL_ATTR_CONNECTION_TIMEOUT is described as follows:

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.

It means SQL_ATTR_CONNECTION_TIMEOUT should also work for long queries, but currently it does not.

Issue Links

• links to: GitHub Pull Request #9862