And also: * Clarify what "closeStatement(StatementHandle)” should do if the statement handle is invalid. Throw or do nothing?
I tried to upgrade Calcite to Avatica 1.8.0 and it’s not trivial. I have pushed my work to the branch https://github.com/julianhyde/calcite/tree/1280-upgrade-avatica <https://github.com/julianhyde/calcite/tree/1280-upgrade-avatica>. I’d like to make sure that implementing the new APIs is possible before we approve the Avatica 1.8.0 release. Can someone take a look? Julian > On May 23, 2016, at 1:40 AM, Julian Hyde <[email protected]> wrote: > > A couple of other problems/questions: > * There still calls within Avatica to the deprecated form of > prepareAndExecute. Wouldn’t it be wise to upgrade all internal uses? > * Why does prepareAndExecuteBatch not have a PrepareCallback parameter like > prepareAndExecute? It makes it difficult to implement it in the obvious way. > > Julian > > >> On May 23, 2016, at 1:13 AM, Julian Hyde <[email protected] >> <mailto:[email protected]>> wrote: >> >> I just logged Avatica issue >> https://issues.apache.org/jira/browse/CALCITE-1254 >> <https://issues.apache.org/jira/browse/CALCITE-1254>, "Support >> PreparedStatement.executeLargeBatch”. >> >> Would fixing cause an incompatible change to the protocol? If so, we should >> consider putting it into 1.8. >> >> Julian >> >
