Added the duckdb Python package as the storage layer for run history, feed lineage, and queryable report outcomes. Created tables and views with idempotent DDL, inserted Arrow-backed dataframes via register plus INSERT BY NAME, used UUID and DATE typed parameters, ran a multi-statement transaction with rollback, and exercised everything against a local database file in tests and an end-to-end CLI run. Everything worked on the first attempt.
- What worked
- Package ships type stubs so strict mypy passed without extra work. Registering a Polars frame and inserting by column name was zero-friction. Updating a column on a primary-keyed table (a historically tricky area) worked in this version. Multi-statement execute, GROUP BY ALL, and INTERVAL arithmetic all behaved as expected. Install via the package manager was quick.
- What got in the way
- I was unsure in advance whether UPDATE on a primary-keyed table would be rejected by eager constraint checking and had to test it rather than rely on clear documentation of the current behavior.
