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

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/04/03 15:19:52 UTC

[jira] [Resolved] (CALCITE-654) Tighten up AvaticaStatement#execute semantics

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

Julian Hyde resolved CALCITE-654.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/0ea085b7.

> Tighten up AvaticaStatement#execute semantics
> ---------------------------------------------
>
>                 Key: CALCITE-654
>                 URL: https://issues.apache.org/jira/browse/CALCITE-654
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>             Fix For: 1.2.0-incubating
>
>         Attachments: CALCITE-654.00.patch, CALCITE-654.01.patch
>
>
> I discovered some mismatch between the existing behavior of JdbcMeta#fetchAndExecute and the more pedantic expectations of my underlying JDBC implementation, particularly around mutation and DDL statements. AvaticaStatement should be more careful about how it represents the underlying response, and we need a way to convey that over the wire.



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