[
https://issues.apache.org/jira/browse/IGNITE-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161531#comment-16161531
]
ASF GitHub Bot commented on IGNITE-6151:
----------------------------------------
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/2638
IGNITE-6151: Impemented getting and setting of the SQL_ATTR_CONNECTION_DEAD
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6151
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2638.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2638
----
commit b710366f8cf58f0fb5b598150601b016217489e9
Author: Igor Sapego <[email protected]>
Date: 2017-09-11T15:05:17Z
IGNITE-6151: Impemented getting and setting of the SQL_ATTR_CONNECTION_DEAD
commit b7cd0bac4ef140c51b08fcb9edce6fc820c1dd64
Author: Igor Sapego <[email protected]>
Date: 2017-09-11T16:13:15Z
IGNITE-6151: Added tests
----
> ODBC: Implement SQL_ATTR_CONNECTION_DEAD connection attribute
> -------------------------------------------------------------
>
> Key: IGNITE-6151
> URL: https://issues.apache.org/jira/browse/IGNITE-6151
> Project: Ignite
> Issue Type: Improvement
> Components: odbc
> Affects Versions: 2.1
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Fix For: 2.3
>
>
> Currently, there is no way to check whether the connection to the server node
> is dead. Implementation of {{SQL_ATTR_CONNECTION_DEAD}} would solve this
> issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
