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/11/17 10:12:58 UTC

[jira] [Updated] (IGNITE-3656) JdbcConnection.setTransactionIsolation should not throw an exception

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

Vladimir Ozerov updated IGNITE-3656:
------------------------------------
    Fix Version/s:     (was: 1.8)
                   2.0

> JdbcConnection.setTransactionIsolation should not throw an exception
> --------------------------------------------------------------------
>
>                 Key: IGNITE-3656
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3656
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc-driver
>    Affects Versions: 1.7
>            Reporter: Valentin Kulichenko
>             Fix For: 2.0
>
>
> {{JdbcConnection.setTransactionIsolation}} now throws {{SQLFeatureNotSupportedException}} which looks incorrect, because:
> * This method can be called by a JDBC tool on startup, even if only select queries will be executed after that.
> * This method does not throw this exception according to JavaDoc.
> Other similar methods should be also revised.
> Corresponding user@ thread: http://apache-ignite-users.70518.x6.nabble.com/Stored-Procedure-td6548.html



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