Skip to content

duckdb support #1366

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 8, 2025
Merged

duckdb support #1366

merged 4 commits into from
Aug 8, 2025

Conversation

Jolanrensen
Copy link
Collaborator

Fixes #1341

duckdb support based on the example I made earlier: #1271

@Jolanrensen Jolanrensen self-assigned this Aug 5, 2025
@Jolanrensen Jolanrensen added the databases JDBC related issues label Aug 5, 2025
@Jolanrensen Jolanrensen requested a review from zaleslaw August 6, 2025 12:14
@Jolanrensen Jolanrensen marked this pull request as ready for review August 6, 2025 12:14
Copy link
Collaborator

@zaleslaw zaleslaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please significantly improve the test coverage with calling all module methods from public API

We need to be sure, that all stuff is working correctly

…errors because variance mismatches in duckdb map values
@Jolanrensen Jolanrensen force-pushed the duckdb-support branch 5 times, most recently from 7a1ad37 to efea146 Compare August 8, 2025 12:04
@Jolanrensen Jolanrensen merged commit fd1fd4d into master Aug 8, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
databases JDBC related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add DuckDB support
2 participants