[
https://issues.apache.org/jira/browse/CALCITE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275709#comment-15275709
]
Julian Hyde commented on CALCITE-1232:
--------------------------------------
Actually, no. Optimize only the common cases, but make all cases operate with
least surprise. That would imply that you send the empty batch to the server,
and the server can handle batches of any size.
> AvaticaStatement should fail fast on executeBatch() if no statements are
> present in the batch
> ---------------------------------------------------------------------------------------------
>
> Key: CALCITE-1232
> URL: https://issues.apache.org/jira/browse/CALCITE-1232
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: avatica-1.8.0
>
>
> Ran into a little bug. I prepared a batch of updates via a PreparedStatement
> but then accidentally called {{executeBatch()}} on another Statement object
> which was currently in scope. This was causing my test to fail because it
> appeared that there were no updates applied in the returned {{int[]}}.
> We should make {{executeBatch()}} on both {{AvaticaStatement}} and
> {{AvaticaPreparedStatement}} fail with an exception if the current batch is
> empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
