Skip to content

fix: migrate documentation generation to DuckDB 2.0 - #328

Merged
Mandukhai-Alimaa merged 1 commit into
dependabot/pip/python-packages-55624eecb0from
fix/duckdb-2-migration
Oct 29, 2026
Merged

Mandukhai-Alimaa merged 1 commit into
dependabot/pip/python-packages-55624eecb0from
fix/duckdb-2-migration

Conversation

@Mandukhai-Alimaa

Copy link
Copy Markdown
Contributor

Stacked on #326. Update documentation generation to handle optional query results and use DuckDB 2.0's statement execution and Arrow conversion APIs.

@Mandukhai-Alimaa
Mandukhai-Alimaa merged commit 5db1f44 into main Oct 29, 2026
3 checks passed
@Mandukhai-Alimaa
Mandukhai-Alimaa deleted the fix/duckdb-2-migration branch October 29, 2026 22:05

def _query(query: str) -> duckdb.DuckDBPyRelation:
result = duckdb.sql(query)
assert result is not None

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Huh, why is this necessary?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

DuckDB 2.0 types sql() as DuckDBPyRelation | None, causing CI type-check failures. The assertion narrows the type for ty, since these queries always return a relation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ah, weird. Ok, thanks

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.

2 participants