You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2017/07/04 14:52:01 UTC

[jira] [Resolved] (IGNITE-5685) JDBC: Prepared statement shouldn't clear params after query execution

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

Andrey Gura resolved IGNITE-5685.
---------------------------------
    Resolution: Fixed

Merged into ignite-2.1 branch.

> JDBC: Prepared statement shouldn't clear params after query execution
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-5685
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5685
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0
>            Reporter: Andrey Gura
>            Assignee: Andrey Gura
>             Fix For: 2.1
>
>
> {{JdbcPreparedStatement}} implementations (Java client, Ignite client node based and thin JDBC) clears query parameters in {{executeXxx}} methods after query execution. It's wrong behavior because {{PreparedStatement}} allows repeatable use.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)