Hello,
This is my 1st question/post so please excuse me in case this is not
the right forum for such questions or it should be posted elsewhere.
I am working on writing a custom adapter. We need to have finer control on
both read/write pipelines. In short, we want the adapter to be an interface
for applications that until now worked with conventional RDBMS which means
support all the SQL constructs *but also provides us the capabilities that
calcite enables*.
Are there any guidelines published for what needs to be extended in order
to support say something as basic as transactions?
Since CalciteMetaImpl commit is explicitly throwing exceptions, its not
possible to do something like...
Connection conn = ...
conn.setAutoCommit(false);
try{
PreparedStatement prep_stmt = conn.prepareStatement(sql.toString());
while(...){
//set values..
prep_stmt.addBatch()/prep_stmt.executeBatch();
}
}
conn.commit();//or abort
Regards,
Kiran
PS: This is the only reference I found when I looked for "calcite
transactions not working".
[1]
https://mail-archives.apache.org/mod_mbox/calcite-dev/201502.mbox/%3ccamctme+wsqq8ehzapyc9-3stzpb7d5ayxy0aa7pzbyucjnh...@mail.gmail.com%3E
