Skip to content

Conversation

@staticlibs
Copy link
Collaborator

This change makes the DuckDBConnection#duplicate() method to return the concrete class instead of the Connection interface to not require users to unwrap the result of the call.

Fixes: #434

This change makes the `DuckDBConnection#duplicate()` method to return
the concrete class instead of the `Connection` interface to not require
users to unwrap the result of the call.

Fixes: duckdb#434
@staticlibs staticlibs merged commit c7cb0f2 into duckdb:main Nov 10, 2025
19 of 20 checks passed
@staticlibs staticlibs deleted the conn_dup branch November 10, 2025 14:42
staticlibs added a commit to staticlibs/duckdb-java that referenced this pull request Nov 10, 2025
This is a backport of the PR duckdb#455 to `v1.4-andium` stable branch.

This change makes the `DuckDBConnection#duplicate()` method to return
the concrete class instead of the `Connection` interface to not require
users to unwrap the result of the call.

Fixes: duckdb#434
staticlibs added a commit that referenced this pull request Nov 10, 2025
This is a backport of the PR #455 to `v1.4-andium` stable branch.

This change makes the `DuckDBConnection#duplicate()` method to return
the concrete class instead of the `Connection` interface to not require
users to unwrap the result of the call.

Fixes: #434
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Why doesn't DuckDBConnection.duplicate return a DuckDBConnection?

1 participant