We’re an open source project, so there is no formal roadmap. Did you search jira? If there is no jira case, log one which describes your problem. I’m not familiar with what changed between JDBC 4.1, 4.2 and 4.3.
Julian > On Aug 24, 2023, at 5:25 AM, Tony Falabella > <[email protected]> wrote: > > Calcite Team, > > Are there any plans to support JDBC 4.2 or 4.3 on the roadmap? > > Also we have code that adds a JdbcSchema to the rootSchema via: > > rootSchema.add(DB_SCHEMA, JdbcSchema.create(rootSchema, DB_SCHEMA, > dataSource, null, DB_SCHEMA)); > > When querying via JPA against an H2 DB that has a table containing a “Binary > Large Object” (a Blob) CalciteJdbc41Connection creates a > CalciteJdbc41PreparedStatement which creates a CalciteResultSet (a subclass > of AvaticaResultSet) which then creates an ArrayIteratorCursor (a subclass of > AbstractCursor) which has this implementation: > > public Blob getBlob() throws SQLException { > throw cannotConvert(“Blob”) > } > > Is there anything I can do to support Blobs/Clobs/Arrays/Refs/etc? Maybe I’m > doing something incorrectly in my Connection initialization. I am NOT > initializing anything with the RelOptPlanner like Rules. It didn’t appear > that I needed to. > > Thanks in advance. > Tony
