You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/02/17 13:04:18 UTC

[jira] [Updated] (IGNITE-2674) ODBC: Cursors should be removed in case of exception only in OdbcRequestHandler.executeQuery() method.

     [ https://issues.apache.org/jira/browse/IGNITE-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov updated IGNITE-2674:
------------------------------------
    Affects Version/s: 1.5.0.final

> ODBC: Cursors should be removed in case of exception only in OdbcRequestHandler.executeQuery() method.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-2674
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2674
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: odbc
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Igor Sapego
>             Fix For: 1.6
>
>
> It is not clear why do we remove query cursor from map in case of exception in OdbcRequestHandler.fetchQuery(). 
> If user has some try-finally construct on the client side and will try to close the request after this exception, he will receive another one from close() method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)