[
https://issues.apache.org/jira/browse/CALCITE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589481#comment-14589481
]
YeongWei commented on CALCITE-705:
----------------------------------
Hi [~julianhyde],
I revisited the implementation around JdbcMeta, I come to realise some
challenges to support DML.
1. JdbcMeta#prepare
If the PreparedStatement belongs to an underlying data source (E.g. MySQL,
HSQLDB, etc), it is unable to deduce the Signature#statementType. Only the ones
belong to Calcite could be deduced.
This includes the list of ColumnMetaData that needs to be responded back to
client which has to be deduced during the prepare stage.
2. JdbcMeta#fetch
If the preparedStatement.execute returns a FALSE then proceed invoke a
JdbcResultSet#Count which takes the preparedStatement.getUpdateCount as argument
Currently #2 is in place but #1 seemed challenging.
Hope to hear from you.
Thanks!
> AvaticaStatement execute method to support DML
> ----------------------------------------------
>
> Key: CALCITE-705
> URL: https://issues.apache.org/jira/browse/CALCITE-705
> Project: Calcite
> Issue Type: New Feature
> Reporter: YeongWei
> Assignee: Julian Hyde
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
