Repository navigation
Why doesn't DuckDBConnection.duplicate return a DuckDBConnection? #434
Description
I consider DuckDBConnection.duplicate():
public Connection duplicate() throws SQLException {
checkOpen();
connRefLock.lock();
try {
checkOpen();
return new DuckDBConnection(DuckDBNative.duckdb_jdbc_connect(connRef), url, readOnly, sessionInitSQL,
autoCommit);
} finally {
connRefLock.unlock();
}
}
Why does it returns a Connection instead of a DuckDBConnection?
Thanks
Activity
[-]Why does `DuckDBConnection.duplicate` does not returns a `DuckDBConnection`?[/-][+]Why doesn't `DuckDBConnection.duplicate` return a `DuckDBConnection`?[/+]Return concrete class as connection duplicate
staticlibs commentedon Nov 9, 2025
@blacelle
Thanks for the report! I think this is an oversight. In theory we may want to return some kind of a side-class there instead of the same class, but currently there are no plans to do so (and later it can just subclass the
DuckDBConnection). Filed #455 to fix this.Return concrete class as connection duplicate
Return concrete class as conn duplicate (1.4)
Return concrete class as conn duplicate (1.4)