Skip to content

Add DuckDB connector (#3) - #2

Merged
harshitboots merged 1 commit into
harshitboots:mainfrom
jadstrike:feature/duckdb-connector
Jun 13, 2026
Merged

Add DuckDB connector (#3)#2
harshitboots merged 1 commit into
harshitboots:mainfrom
jadstrike:feature/duckdb-connector

Conversation

@jadstrike

Copy link
Copy Markdown
Contributor

What this adds

DuckDB connector, as requested in the README's next-targets list (issue #3).

  • src/connectors/duckdb_conn.py — follows the standard connect / list_tables / fetch_table pattern used by the other five connectors. Takes a .duckdb file path (DuckDB is in-process, so no host/credentials needed).
  • DuckDB option in the Database Connectors section of the Streamlit UI (file path + table inputs).
  • duckdb added to requirements.txt and pyproject.toml.

Tests

Added TestDuckDBConnector with three tests (list_tables, fetch_table, row limit). They create a temp DuckDB file via tmp_path, so they run anywhere — no external services or credentials required.

pytest tests/ -v

All existing tests still pass.

README

  • DuckDB usage snippet under Database Connectors
  • Connector status table: DuckDB → Stable (auth: file path)
  • Removed DuckDB from the next-targets table and checked the roadmap box

- New connector src/connectors/duckdb_conn.py following the standard
  connect/list_tables/fetch_table pattern
- DuckDB option in the Database Connectors UI (file path + table)
- Tests covering list_tables, fetch_table and the row limit
- README: usage snippet, connector status table and roadmap updated
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