database-tycoon 0.2.3__tar.gz → 0.2.5__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/.gitignore +7 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/CHANGELOG.md +115 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/PKG-INFO +8 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/README.md +3 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/pyproject.toml +11 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/__init__.py +1 -1
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/cli.py +37 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/city.py +6 -7
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/data.py +7 -1
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/db.py +125 -83
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/docs.py +3 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/doctor.py +114 -12
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/explore.py +7 -0
- database_tycoon-0.2.5/src/tycoon/commands/fire.py +336 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/history.py +4 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/init.py +102 -35
- database_tycoon-0.2.5/src/tycoon/commands/layers.py +312 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/notify.py +3 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/observability.py +5 -5
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/register.py +9 -8
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/run_all.py +15 -10
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/schedule.py +2 -2
- database_tycoon-0.2.5/src/tycoon/commands/schema_listing.py +120 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/semantics.py +13 -9
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/setup.py +6 -6
- database_tycoon-0.2.5/src/tycoon/commands/source_explorer.py +259 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/sources.py +17 -9
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/status.py +17 -7
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/sync_cmd.py +9 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/transform.py +127 -34
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/config.py +128 -33
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/core/events.py +14 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/core/history.py +26 -28
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/dbt_profiles.py +4 -2
- database_tycoon-0.2.5/src/tycoon/ingestion/destination.py +46 -0
- database_tycoon-0.2.5/src/tycoon/ingestion/pipeline_state.py +278 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/runner.py +136 -9
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/source_manager.py +41 -12
- database_tycoon-0.2.5/src/tycoon/motherduck.py +62 -0
- database_tycoon-0.2.5/src/tycoon/observability/dbt_builds.py +50 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/observability/dbt_capture.py +12 -2
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/observability/dlt_capture.py +17 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/project.py +17 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/scaffolding/osi_generator.py +48 -13
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/scaffolding/templates.py +31 -4
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/sync.py +9 -5
- database_tycoon-0.2.5/src/tycoon/utils/query_output.py +197 -0
- database_tycoon-0.2.5/src/tycoon/utils/sql_guard.py +87 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/dbt_manifest.py +63 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/loader.py +63 -19
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/models.py +5 -1
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/demo/factory.py +2 -1
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/blocks.py +6 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/build.py +36 -1
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/pricing.py +4 -2
- database_tycoon-0.2.3/src/tycoon_city/web_dist/assets/index-BJC7D2Ta.js → database_tycoon-0.2.5/src/tycoon_city/web_dist/assets/index-c_sgYUZt.js +209 -209
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/web_dist/index.html +12 -3
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/webserve.py +12 -5
- database_tycoon-0.2.3/src/tycoon/ingestion/ducklake_config.py +0 -68
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/LICENSE +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/THIRD-PARTY.md +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/__main__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/fivetran.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/profiles.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/run.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/start.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/commands/stop.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/constants.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/core/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/core/metadata.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/catalog.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/fivetran_client.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/fivetran_sync.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/mta_bus_speeds_pipeline.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/mta_pipeline.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/nyc_dot_pipeline.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/source_installer.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/ingestion/sources/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/layers.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/metadata_backends/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/metadata_backends/duckdb_file.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/notify.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/observability/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/observability/store.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/quack.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/scaffolding/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/scaffolding/dbt_generator.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/scaffolding/observability_dbt.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/scaffolding/rill_generator.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/scaffolding/schemas/osi-v0.1.1.schema.json +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/schedule.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/README +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/data/input/widgets.csv +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/dbt_project/dbt_project.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/dbt_project/models/marts/fct_widget_summary.sql +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/dbt_project/models/marts/schema.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/dbt_project/models/staging/schema.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/dbt_project/models/staging/stg_widgets.sql +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/dbt_project/profiles.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/csv-import/tycoon.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/github-analytics/template.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/github-analytics/tycoon.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/nyc-transit/README +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/nyc-transit/tycoon.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/weather-station/template.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/templates/weather-station/tycoon.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/utils/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/utils/console.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/utils/duckdb_utils.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/utils/process.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/venv.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon/yaml_merge.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/column_lineage.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/errors.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/osi.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/retention.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/run_history.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/sql_lineage.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/catalog/tycoon_project.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/cli.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/demo/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/demo/cli.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/demo/project.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/demo/semantic.yml +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/achievements.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/city_json.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/cli.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/measured.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/export/run_json.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/__init__.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/build_replay.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/channels.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/city.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/contracts.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/generator.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/layout.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/logistics.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/road_junctions.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/schemas/request_schema.json +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/schemas/shipment_schema.json +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/signals.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/tiles.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_arterials.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_blocks.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_endings.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_frontage.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_hierarchy.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_network.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_plan.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_precincts.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_rows.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_streets.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_texture.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/sim/town_zoning.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/theme_data.py +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/themes/default/spritesheet.png +0 -0
- {database_tycoon-0.2.3 → database_tycoon-0.2.5}/src/tycoon_city/themes/default/theme.toml +0 -0
|
@@ -1,5 +1,120 @@
|
|
|
1
1
|
All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
2
2
|
|
|
3
|
+
## [0.2.5] - 2026-11-20
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- **`tycoon data sources run`, `data sources run-all` and `data run-all` can load into a MotherDuck raw database** ([#447][], part of [#430][]). With `database.raw: md:<name>` (or `motherduck:<name>`) the commands used to exit before running anything; they now hand the raw target to the runner, which builds `dlt.destinations.motherduck(...)` through one helper, `raw_destination()`, and every source shim uses the same helper. A raw database that is a local file takes the same path as before. Editing `database.raw` and `database.warehouse` in `tycoon.yml` is not enough to move a whole project: dbt reads `dbt_project/profiles.yml`, which neither that edit nor `tycoon register warehouse --type motherduck` touches (the command writes only `tycoon.yml`), so `transform` would keep building local files. Point the profile's `path` and its `raw` attach at the `md:` names too, or start a new project with `tycoon init` choosing MotherDuck, which writes both. Things to know before switching a project from a file to `md:`: the MotherDuck database must exist first (dlt does not create it; the error says so), `MOTHERDUCK_TOKEN` must be exported in the shell that runs tycoon (tycoon does not read `.env` files), dlt's MotherDuck loader needs `pyarrow` (install the `database-tycoon[motherduck]` extra, see [#459][]; the error says so), and dlt's incremental cursors start over because dlt keeps them in the destination, so the first `md:` run reloads from each source's initial value and rows already in the local file are not copied. The legacy-table warning and the run capture into `.tycoon/metadata.duckdb` do not run for an `md:` raw, so run history is not recorded for those loads. The three built-in demo pipelines (`nyc-dot`, `mta-gtfs`, `mta-bus-speeds`) stay local-only. A catalog source whose `_run.py` was installed before this release has to be re-installed to load into MotherDuck; the error names the file to delete.
|
|
8
|
+
- **`tycoon semantics scaffold` and the post-transform OSI scaffold read a MotherDuck warehouse** ([#298][]). With `database.warehouse: md:<db>` both open the database through `config.warehouse_target` and read only that catalog's tables, so the other databases on the account are never listed. Dataset sources come out as `<db>.<schema>.<table>`. With no MotherDuck token, `semantics scaffold` exits 1 before connecting with the same `No MotherDuck token for md:<db>` line as `data query`, and the automatic scaffold is skipped with a one-line note, because DuckDB would otherwise open a browser sign-in. The token sources are the ones `data query` accepts, so a token saved at `~/.duckdb/motherduck_token` does not count. If the database cannot be opened or read, `semantics scaffold` prints the error with the token redacted and exits 1 without touching `osi.yaml`, and the automatic scaffold prints the same error as a one-line note. `motherduck:` and upper-case `MD:` targets are recognised as MotherDuck too. Local DuckDB warehouses produce the same output as before.
|
|
9
|
+
- **`database-tycoon[motherduck]` extra for MotherDuck raw loads** ([#459][], part of [#430][]). dlt loads into MotherDuck through Parquet and needs `pyarrow`, which a base install does not carry. The new extra pulls in `dlt[motherduck]` at the same exact version as the base `dlt[duckdb]` pin, which adds `pyarrow` and nothing else to `uv.lock`. A base install is unchanged. The missing-`pyarrow` error now names `pip install 'database-tycoon[motherduck]'` instead of `pip install pyarrow`, and `data sources run` and `run-all` print pipeline errors without letting Rich read `[...]` as markup, so the extra's name survives on screen.
|
|
10
|
+
- **Failing tests in the terminal: `tycoon fire` and `tycoon firehouse`** ([#306][]). `tycoon fire` lists the failing tests (a test in `fail` or `error`) that the 3D city draws as buildings on fire, and `tycoon firehouse` counts them as fire trucks on duty. Each test counts by its newest result across the captured runs, as in the city, so a later `dbt run` that runs no tests leaves earlier failures listed. A model that failed to build is not a fire: both commands then say how many models failed and point at `tycoon data history`. `fire --run <id>` shows one run and takes the run ids `tycoon data history` prints or a dbt invocation id prefix; an ambiguous prefix is an error.
|
|
11
|
+
- **`tycoon data layers`** ([#306][]). The sources, staging, intermediate and marts layers, with the vendor of every object (dlt, Fivetran or dbt). Each model shows its status in its latest run and when it last built successfully, and each layer's summary names the newest successful build in the layer and counts the models that failed in their latest run.
|
|
12
|
+
- **`tycoon data sources explore`** ([#306][]). Inspect a source's schema, sample rows and run history without leaving the terminal. `--sample` takes 1 or more rows.
|
|
13
|
+
- **`tycoon data query --format`** ([#391][]). `--format csv`, `json` or `markdown` prints the result rows and nothing else, so a script or notebook can read them without parsing a terminal table. In JSON, a NaN or infinite `DOUBLE` is `null` so that strict parsers can read the output; in every machine format a `BLOB` is hex and an `INTERVAL` is an ISO 8601 duration. The default `table` format no longer squashes a wide result until every header reads `ro…`: when the columns don't fit the terminal, each row prints as its own block of column names and values, like `psql`'s expanded display, and an empty result lists the column names instead.
|
|
14
|
+
- **`tycoon data schema` can show one database or one schema** ([#393][]). `--raw` and `--warehouse` pick one database, and `--schema` takes a schema name or a glob such as `'raw_*'`. dlt's `_dlt_*` bookkeeping tables are now left out by default, with a count of how many were hidden; `--include-dlt` lists them. On a MotherDuck database, `--exact` counts only the tables left after these filters, and with `--raw` or `--warehouse` the MotherDuck token check covers only the database shown.
|
|
15
|
+
- **A mental model of the city map, for contributors reviewing city PRs** ([#323][]). `docs/city/mental-model.md` maps each data-stack concept (source, table, dbt model, test, run, freshness SLA, docs coverage) to what it becomes on the `tycoon city` map and the `city.json` field it comes from, walks one worked example from the `csv-import` template to the rendered city, and gives reviewers a table of which layer a PR touches plus a short checklist. `docs/city/` is withheld from the published docs site, so the page renders only under `tycoon docs serve` and on GitHub.
|
|
16
|
+
|
|
17
|
+
### Changed
|
|
18
|
+
|
|
19
|
+
- **Working on tycoon needs uv 0.12.22 or later** ([#493][]). `uv.lock` depended on which uv last locked it: older releases wrote it in an older format, so a one-line dependency change could come out as a much larger diff. The minimum now lives in `required-version` in `pyproject.toml`, CI installs the newest uv that satisfies it, and `uv.lock` is relocked once at the current format (no package versions change). For contributors; installing tycoon from PyPI is unaffected.
|
|
20
|
+
- **The publish workflow refuses a tag that isn't on `main`** ([#473][]). The release process tags `main` after the release branch merges into it, but nothing checked that. v0.2.4 was tagged on its release branch and published to PyPI while `main` still pointed at v0.2.3, and `main` caught up three days later. Preflight now fails when the tagged commit is not on `main`, before anything builds. A tag pushed too early can stay where it is if the promotion PR merges as a merge commit: merge it, then re-run the job. A squash or rebase merge never puts the tagged commit on `main`, so the tag has to be re-created there.
|
|
21
|
+
- **Steps that run after a load skip a MotherDuck raw database** ([#448][], part of [#430][]). The legacy-table warning, the dlt run capture into `.tycoon/metadata.duckdb`, the dbt staging auto-scaffold after `data sources run`, and `tycoon data analyze` all assume the raw database is a local file. On `database.raw: md:<name>` the first two skip silently and the auto-scaffold skips with one line. `tycoon data analyze` is an explicit command, so it exits 1 with one line saying it reads a local raw file, as it already did in v0.2.3 and v0.2.4. Run history for an `md:` raw is therefore not captured yet. A project on a local raw file is unchanged. `src/tycoon/ingestion/ducklake_config.py`, which had no callers, is deleted.
|
|
22
|
+
- **`tycoon init` scaffolds a new dbt project inline, not as a sibling repo** ([#259][], PR [#260][]). "Create new" in the dbt wizard step now defaults to `<project>/dbt_project` instead of `../<project>-dbt`, matching the Rill step's existing inline default and the `dbt_project_dir` schema default, so a fresh `tycoon init` produces one folder, one `git init`, instead of two repos that have to be cloned and tracked separately. Registering an *existing* dbt project (local path or GitHub URL) is unaffected and still accepts a sibling location; a cloned URL still defaults beside the project rather than inside it, since cloning brings its own `.git`. The project's parent-directory boundary (#65) is now enforced the moment a path is entered in the wizard, not only the first time a command reads it from `tycoon.yml`. When tycoon itself scaffolds the inline project, the generated `.gitignore` no longer ignores its `dbt_project/profiles.yml` (it holds relative DuckDB paths only, no secrets), so a fresh clone can run `tycoon data transform` without regenerating it by hand. A dbt project tycoon did not create, such as one the wizard detected, keeps its `profiles.yml` ignored, since it may hold credentials.
|
|
23
|
+
|
|
24
|
+
### Removed
|
|
25
|
+
|
|
26
|
+
- **Jira PTC keys are no longer accepted in PR titles, and the Jira sync workflow is gone** ([#351][]). The project moved its tracking from the Jira PTC board to GitHub issues and the Tycoon CLI project on 2026-10-09, so the PR title check now accepts `gh-<N>` scopes only, and `CONTRIBUTING.md` and the contributor skills no longer describe `PTC-<N>` as an option. `.github/workflows/jira-sync.yml` is deleted: its `JIRA_EMAIL` and `JIRA_API_TOKEN` secrets were never set, so every run exited without syncing anything. Existing commits, changelog entries and release notes that cite `PTC-<N>` keys are unchanged. For contributors.
|
|
27
|
+
|
|
28
|
+
### Security
|
|
29
|
+
|
|
30
|
+
- **Releases publish with `pypa/gh-action-pypi-publish` v1.14.3** ([#500][]). The TestPyPI and PyPI jobs in `publish.yml` pinned v1.14.2, which advisory GHSA-5xjx-3w67-w9x9 lists as affected. Both now pin v1.14.3 by commit SHA. For contributors; installing tycoon from PyPI is unaffected.
|
|
31
|
+
- **Local secret files can no longer be committed by accident** ([#410][]). The repository's `.gitignore` now covers `.env`, `.env.*` and any `.dlt/secrets.toml`, so credentials a contributor keeps for local runs stay out of commits in this public repo. `.env.example` stays committable, and a test fails if these rules are ever dropped. This changes nothing in the published package.
|
|
32
|
+
- **A MotherDuck token in a connection string no longer shows up in output** ([#510][]). With a source such as `md:analytics?motherduck_token=${MOTHERDUCK_TOKEN}`, `tycoon data sync` printed the full string on every copied-table line, and the token could also appear in skip reasons and in `Sync failed`. `tycoon city` printed it in its `Serving` line, logged it, and could repeat it in a catalog error. All of these now show `md:analytics`, with the query string dropped or the token masked; the full string is still used to connect.
|
|
33
|
+
- **Locked dependencies with open security advisories are refreshed** ([#526][]). `uv.lock` now resolves GitPython 3.2.1, certifi 2026.10.23, anyio 4.14.2, urllib3 2.8.0, msgpack 1.2.4, fsspec 2026.9.0, setuptools 84.2.1, idna 3.20 and Pygments 2.21.0. The `docs` extra pins mkdocs-material 9.8.1, which brings pymdown-extensions 13.1 and fixes an XSS in the docs site's search suggestions. The city's web tooling moves to vite 6.4.6. A plain `pip install database-tycoon` already picked up the patched transitive versions; this changes what developers and CI install. sqlparse stays below 0.6.0 until dbt-core allows it (#347).
|
|
34
|
+
|
|
35
|
+
### Fixed
|
|
36
|
+
|
|
37
|
+
- **The city inspector lists off-map dbt sources under UPSTREAM** ([#387][]). v0.2.4 added `objects[].dbt.external_upstream` to the export, but the inspector still listed only the model's edges, so a staging model whose inputs all live outside the warehouse showed its upstream as "none". The inspector now lists those sources after the edges, marked as outside this warehouse and not measured, with dbt's freshness verdict when there is one. They have no link to fly to, because the city draws no building for them. "none" now means the model has no inputs at all. Clicking text in a city panel, or dragging from a panel onto the map, no longer closes the inspector or selects the building behind the pointer.
|
|
38
|
+
- **`tycoon doctor` no longer calls a working `.venv` without tycoon "empty or broken"** ([#392][]). A project whose `.venv` was healthy, but with tycoon installed as a separate uv tool, got told to run `tycoon setup --force`, which re-resolves every dependency and in one project downgraded duckdb and dbt-core. Doctor now checks whether the `.venv` can run Python. If it can, doctor says built-in sources and dbt keep working from the tool install, but catalog sources need tycoon in the `.venv`: their dependencies install into the `.venv` while tycoon imports them from its own environment. It suggests `uv add database-tycoon` (or `uv pip install --python .venv database-tycoon` without a `pyproject.toml`), noting that tycoon's exact pins will apply. The rebuild advice is kept for a `.venv` that is empty, a plain file, or missing its interpreter. On Windows, doctor also finds tycoon at `.venv/Scripts/tycoon.exe`, not only `.venv/bin/tycoon`.
|
|
39
|
+
- **An `md:` target with no MotherDuck token fails at once instead of opening a browser sign-in** ([#460][]). With no token, DuckDB's MotherDuck extension starts a browser sign-in and waits, so `tycoon data query` on an `md:` warehouse sat on the sign-in page for about a minute, and in a script or CI job it hung. `data query`, `data schema` and `data sync` now check before they connect and exit 1 with `No MotherDuck token for md:<db>: export MOTHERDUCK_TOKEN and run again.` A token counts when `MOTHERDUCK_TOKEN` or `motherduck_token` is set or when the connection string carries `motherduck_token=<value>`. The file `~/.duckdb/motherduck_token` does not count: on DuckDB 1.5.4 a valid token in that file, with both variables unset, still started the browser sign-in. Projects on local DuckDB files never reach the check.
|
|
40
|
+
- **`tycoon city` refuses an `md:` or `motherduck:` catalog with no MotherDuck token** ([#460][]). `tycoon city --path md:<db>`, `tycoon-city` and `tycoon-city export` now exit 1 with the same one-line message instead of starting the server and opening a browser sign-in on the first request. The renderer accepts the same token sources as the CLI: `MOTHERDUCK_TOKEN` or `motherduck_token` in the environment, or `motherduck_token=<value>` in the catalog string. Local files and project directories are unaffected.
|
|
41
|
+
- **`tycoon city`, `tycoon-city` and `tycoon data sync` accept a `motherduck:` target** ([#446][], follow-up to [#308][]). v0.2.4 taught the rest of tycoon the `motherduck:` prefix, but the city renderer and `data sync` still only recognised `md:`. The catalog name shown in the city's status strip now drops the `motherduck:` prefix the same way it drops `md:`, and a `motherduck:` catalog is not looked up as a file for `pricing.toml` or for the load cache. `tycoon_city` does not import `tycoon`, so it carries its own copy of the prefix rule.
|
|
42
|
+
- **Projects no longer share dlt state, so a same-named source can't load duplicate rows** ([#394][]). Tycoon ran every pipeline in dlt's default `~/.dlt/pipelines`, which every project on the machine shares, and named each pipeline after its source. Two projects with a `github` source shared one incremental cursor: after one project moved it, the other reloaded rows it already had, with no error. Each project now keeps its dlt state in `<project>/.tycoon/dlt/pipelines`, which a new project's `.gitignore` excludes and which carries its own `.gitignore` for existing projects. The first run of each pipeline after upgrading copies the shared state in only when it matches what that project last loaded. When it doesn't, dlt restores the project's own state from its raw database, and a project that never loaded the dataset starts fresh. Where nothing can be checked, the shared state is copied with a warning, as the run would have used it before. The shared directory is never moved or deleted. `tycoon doctor` reports what each source's next run will do, and a `DLT_DATA_DIR` you set yourself is left alone. If `.tycoon/dlt/` can't be written, for example on a read-only checkout, the run warns in one line and keeps using the shared directory, so it still loads.
|
|
43
|
+
- **dlt trace capture follows the pipeline's working directory** ([#394][]). Run-history capture read `trace.pickle` from a hard-coded `~/.dlt/pipelines`, so a pipeline that ran anywhere else, for example with `DLT_DATA_DIR` set, loaded fine but never showed up in `dlt_trace_runs` or the byte and timing detail of `tycoon data history`. Capture now reads from the directory the pipeline itself used, and falls back to dlt's own default (`DLT_DATA_DIR`, else `~/.dlt/pipelines`) when it doesn't know the pipeline.
|
|
44
|
+
- **`duckdb` is pinned to 1.5.4, which builds `QUALIFY` over cast columns as a table** ([#339][]). On the previous pin, `duckdb==1.5.2`, a `QUALIFY` window over columns cast in a CTE failed with `INTERNAL Error: Failed to bind column reference` once wrapped in `CREATE TABLE AS`, which is how dbt builds a table model. A staging dedupe of the form "cast in a CTE, then `qualify row_number() over (...) = 1`" therefore failed under `tycoon data transform`, and on MotherDuck targets too. DuckDB 1.5.4 fixes it; `uv.lock` changes only the `duckdb` entry. Existing warehouse files need no migration: a file written by 1.5.2 opens and accepts writes under 1.5.4. MotherDuck's server runs its own DuckDB, and the issue reports a similar crash there on a different code path (`TopNWindowElimination`) that this pin does not address.
|
|
45
|
+
- **`tycoon city`: the legend no longer shows through the detail panel** ([#382][]). Both panels are translucent and sit on the right edge, so a tall detail panel stacked its text over the legend's. The legend now hides while a building is selected and comes back when the panel closes.
|
|
46
|
+
- **`tycoon city`: long model and test names wrap instead of being clipped** ([#383][]). The detail panel split model names mid-word (`station_informa` / `tion`) and cut long dbt test names off at its right edge. Identifiers now wrap after an underscore or dot, and anything still too long wraps inside the panel rather than running past it.
|
|
47
|
+
- **`tycoon city`: HUD panels no longer run off the window edges** ([#384][]). A trackpad pinch over a HUD panel zoomed the whole page instead of the city, which cuts the panels and the header chips off at both edges; that is the likeliest cause of the report and reproduces in headless Chrome. A pinch now only zooms the camera over the canvas and does nothing elsewhere. The page cancels every Ctrl+wheel event to do this, so Ctrl plus a mouse wheel no longer zooms the browser either; keyboard zoom (Cmd/Ctrl with + and -) still works. The panels also cap their width at the window width.
|
|
48
|
+
- **`tycoon city`: views no longer show `rows 0`** ([#388][]). A view stores no rows, so the catalog reports 0 for it as a placeholder, and the detail panel, the hover tooltip and the Stats table printed that 0 as if the view were empty. They now say the rows are not counted.
|
|
49
|
+
- **`tycoon city`: the HUD labels its two object counts** ([#389][]). The footer said `90 objects` and the run replay header said `109 nodes off this map`, with nothing to say they count different things. The footer now reads `90 tables and views`, and the run header reads `109 dbt nodes not matched to a building (tests, seeds, snapshots, models outside this catalog)`. Only models are matched to buildings, so a seed or snapshot counts here even when its table has one.
|
|
50
|
+
- **An invalid `tycoon.yml` no longer crashes the CLI at startup** ([#378][]). Help is available at every command level. `--version`, `init`, `city`, `docs` and `run` remain available. `doctor` reports the error and skips dbt and Rill path checks until the file is fixed. Commands such as `setup` and `data query` exit with a validation message.
|
|
51
|
+
- **`--help` no longer shows literal RST double backticks** ([#443][]). Help text comes from command docstrings, and several of them used RST double-backtick markup, which `--help` prints as-is. `tycoon setup`, `tycoon data sources add`, `tycoon data clean`, `tycoon docs`, `tycoon doctor`, `tycoon notify`, `tycoon observability`, `tycoon register` and `tycoon schedule` now use single backticks. A test walks every registered command and fails if a help text, short help, epilog or option help contains a double backtick.
|
|
52
|
+
- **A Google Sheets run no longer opens a browser sign-in when given the wrong key file** ([#349][]). The run shim passed any JSON at `credentials_path` to dlt, which reads an OAuth client file as interactive credentials and opens a browser, so cron and CI runs hung. A path that isn't a file used to pass no credentials at all, with the same result. The shim now stops with an error that names the file and says how to create a service-account key. A blank path still falls back to dlt's own credential lookup. Projects that added the source earlier pick up the new shim when the source is reinstalled.
|
|
53
|
+
|
|
54
|
+
[#349]: https://github.com/Database-Tycoon/tycoon-cli/issues/349
|
|
55
|
+
[#526]: https://github.com/Database-Tycoon/tycoon-cli/issues/526
|
|
56
|
+
[#510]: https://github.com/Database-Tycoon/tycoon-cli/issues/510
|
|
57
|
+
[#443]: https://github.com/Database-Tycoon/tycoon-cli/issues/443
|
|
58
|
+
[#410]: https://github.com/Database-Tycoon/tycoon-cli/issues/410
|
|
59
|
+
[#378]: https://github.com/Database-Tycoon/tycoon-cli/issues/378
|
|
60
|
+
[#500]: https://github.com/Database-Tycoon/tycoon-cli/issues/500
|
|
61
|
+
[#493]: https://github.com/Database-Tycoon/tycoon-cli/issues/493
|
|
62
|
+
[#473]: https://github.com/Database-Tycoon/tycoon-cli/issues/473
|
|
63
|
+
[#460]: https://github.com/Database-Tycoon/tycoon-cli/issues/460
|
|
64
|
+
[#446]: https://github.com/Database-Tycoon/tycoon-cli/issues/446
|
|
65
|
+
[#430]: https://github.com/Database-Tycoon/tycoon-cli/issues/430
|
|
66
|
+
[#447]: https://github.com/Database-Tycoon/tycoon-cli/issues/447
|
|
67
|
+
[#448]: https://github.com/Database-Tycoon/tycoon-cli/issues/448
|
|
68
|
+
[#459]: https://github.com/Database-Tycoon/tycoon-cli/issues/459
|
|
69
|
+
[#430]: https://github.com/Database-Tycoon/tycoon-cli/issues/430
|
|
70
|
+
[#392]: https://github.com/Database-Tycoon/tycoon-cli/issues/392
|
|
71
|
+
[#394]: https://github.com/Database-Tycoon/tycoon-cli/issues/394
|
|
72
|
+
[#393]: https://github.com/Database-Tycoon/tycoon-cli/issues/393
|
|
73
|
+
[#391]: https://github.com/Database-Tycoon/tycoon-cli/issues/391
|
|
74
|
+
[#351]: https://github.com/Database-Tycoon/tycoon-cli/issues/351
|
|
75
|
+
[#339]: https://github.com/Database-Tycoon/tycoon-cli/issues/339
|
|
76
|
+
[#298]: https://github.com/Database-Tycoon/tycoon-cli/issues/298
|
|
77
|
+
[#323]: https://github.com/Database-Tycoon/tycoon-cli/issues/323
|
|
78
|
+
[#260]: https://github.com/Database-Tycoon/tycoon-cli/pull/260
|
|
79
|
+
[#259]: https://github.com/Database-Tycoon/tycoon-cli/issues/259
|
|
80
|
+
[#382]: https://github.com/Database-Tycoon/tycoon-cli/issues/382
|
|
81
|
+
[#383]: https://github.com/Database-Tycoon/tycoon-cli/issues/383
|
|
82
|
+
[#384]: https://github.com/Database-Tycoon/tycoon-cli/issues/384
|
|
83
|
+
[#388]: https://github.com/Database-Tycoon/tycoon-cli/issues/388
|
|
84
|
+
[#389]: https://github.com/Database-Tycoon/tycoon-cli/issues/389
|
|
85
|
+
[#306]: https://github.com/Database-Tycoon/tycoon-cli/issues/306
|
|
86
|
+
|
|
87
|
+
## [0.2.4] - 2026-11-07
|
|
88
|
+
|
|
89
|
+
### Fixed
|
|
90
|
+
|
|
91
|
+
- **`tycoon data run-all` runs tycoon's own dbt, not whichever is first on `PATH`** ([#439][]). `data transform` already preferred the dbt installed next to the Python running tycoon; `run-all` looked it up on `PATH` instead. A global dbt Fusion on `PATH` rewrote the warehouse file in a storage format the project's dbt-duckdb could not read, and a `uv tool install` with no dbt on `PATH` ingested and then failed with "`dbt` not found on PATH". `run-all` now resolves dbt the same way `data transform` does.
|
|
92
|
+
- **`tycoon data run-all` records its dbt build in run history** ([#326][]). After `run-all`, `.tycoon/metadata.duckdb` had no `dbt_runs` or `dbt_nodes` rows, so a project that only used `run-all` showed no dbt history and the city had no build traffic or test signal for it. Its dbt step now records the build the same way `transform build` does.
|
|
93
|
+
- **`tycoon data status` shows when each dbt layer was last built** ([#390][]). The staging, intermediate and marts panels always said "last build never", even when `tycoon data history` listed successful builds of those models. Status looked models up by bare name, but the run ledger stores each node under its dbt `unique_id` (`model.<project>.<name>`), so nothing ever matched. It now matches on `unique_id`. The ledger also stores build start times as local wall-clock time and status read them as UTC, which would have made a build two hours old in New York show as "6h ago"; status now reads them in local time. Ledgers written by earlier versions need no migration: their builds show up on the next `data status`.
|
|
94
|
+
- **City labels no longer draw on top of each other** ([#385][]). District and civic chips were placed independently, so on a real catalog `main_semantic` and `main_intermediate` merged into one unreadable line and the library and firehouse chips stacked on one spot. A colliding chip now moves up or down by a chip height or two; larger districts keep their spot, and a civic chip that still has no room is hidden until the view changes.
|
|
95
|
+
|
|
96
|
+
- **`tycoon city` names the dbt sources a staging model reads, even when they live outside the warehouse** ([#387][]). When a project's sources point at a separate database (for example `database: raw`, an attached DuckDB file or a DuckLake), none of them is an object in the warehouse the city reads, so lineage stopped at staging and every staging model listed its upstream as "none". The export now lists those sources on each model under `objects[].dbt.external_upstream`, with dbt's freshness verdict when `sources.json` has one; a source read through an ephemeral model is listed on the model that uses it. The city still draws no building for them, because nothing about them can be measured from the warehouse.
|
|
97
|
+
|
|
98
|
+
- **`data history` no longer marks a successful dbt build as failed** ([#341][]). dbt 1.10 and later report exposures and saved queries as `no-op`, and tycoon counted every status outside a fixed list of good ones as an error, so a clean build that touched an exposure showed `✗`. tycoon now counts only dbt's failure statuses (`error`, `fail`, `runtime error`, `partial success`), so a status dbt adds later doesn't turn into a false failure. `dbt_runs.success` in `.tycoon/metadata.duckdb` was NULL on every row, because tycoon read a top-level `success` key that `run_results.json` doesn't have. It now comes from dbt's exit code, or from the node statuses when the exit code isn't known.
|
|
99
|
+
- **Failed dbt runs show up in `data history`** ([#377][]). A run that failed before dbt wrote `run_results.json`, such as an unknown target or a DuckDB file locked by another run, was never recorded, so the history only listed successes. `tycoon data transform` now records it as failed, and `data history show` gives dbt's exit code and a one-line error summary: the first failed node's message, or dbt's own error text when no node ran. dbt's output still prints as it runs; tycoon keeps its last lines for the summary. A run whose selector matched nothing, which dbt treats as a success, is now flagged with `!` and "nothing ran" instead of a green tick.
|
|
100
|
+
- **A `motherduck:` warehouse or raw target is no longer treated as a local file** ([#308][]). DuckDB and dbt-duckdb accept `motherduck:<name>` as well as `md:<name>`, but tycoon only recognised `md:`, so `database.warehouse: motherduck:x` resolved to `<root>/motherduck:x` and failed with "Database not found". One `is_motherduck()` helper in `tycoon.project` now decides, and `tycoon register`, `tycoon init`, dbt profile detection and secret redaction use it. Projects on `md:` or a local file behave as before; only strings that start with `motherduck:` change meaning. The city renderer and `tycoon data sync` follow in a later PR.
|
|
101
|
+
|
|
102
|
+
### Changed
|
|
103
|
+
|
|
104
|
+
- **`tycoon data query` refuses writes on a MotherDuck database unless you pass `--allow-writes`** ([#309][]). DuckDB cannot open an `md:` database read-only, so `data query` ran whatever it was given with the permissions of your token: `tycoon data query "DROP TABLE ..."` ran against production. tycoon now classifies each statement with sqlglot and, on an `md:` warehouse or `--raw` database, runs only SELECT, WITH, `FROM tbl`-first queries, `TABLE tbl`, VALUES, set operations, DESCRIBE, SHOW, SUMMARIZE, PIVOT, UNPIVOT and EXPLAIN of those. Anything else exits 1 before connecting, with `Refusing to run DROP against MotherDuck (md:x). On MotherDuck, 'data query' only runs SELECT, WITH, FROM, TABLE, VALUES, DESCRIBE, SHOW, SUMMARIZE, PIVOT, UNPIVOT and EXPLAIN. Pass --allow-writes to run other statements.` Every statement in a multi-statement input is checked, and a statement sqlglot cannot parse, or a query nested too deeply to parse, is refused too. **This changes behaviour for MotherDuck users who wrote through `data query`: add `--allow-writes` to those commands and scripts.** The check reads statement types only. Function calls inside a SELECT are not inspected, so `SELECT nextval('s')`, `read_csv` on a path or URL, or `FROM checkpoint()` still run without the flag. It guards against accidents and is not a permission boundary; scope your token if that matters. Local DuckDB files already open read-only and are unaffected.
|
|
105
|
+
- **`tycoon data schema` estimates row counts on a MotherDuck database** ([#310][]). It ran an exact `count(*)` on every table, which is slow and spends compute on a large account. It now reads `estimated_size` from `duckdb_tables()` and prints each figure as `~1,000 rows (estimate)`. The estimate does not drop after deletes (100,000 rows less half of them still shows `~100,000`), so treat it as an upper bound on a table that has lost rows. A view has no catalog estimate and prints `view (use --exact to count)`; a table whose catalog reports none prints `no estimate (use --exact to count)`. Pass `--exact` to count every table and view as before. Local DuckDB files are unchanged and still show exact counts, with or without `--exact`.
|
|
106
|
+
|
|
107
|
+
[#308]: https://github.com/Database-Tycoon/tycoon-cli/issues/308
|
|
108
|
+
[#309]: https://github.com/Database-Tycoon/tycoon-cli/issues/309
|
|
109
|
+
[#310]: https://github.com/Database-Tycoon/tycoon-cli/issues/310
|
|
110
|
+
[#341]: https://github.com/Database-Tycoon/tycoon-cli/issues/341
|
|
111
|
+
[#377]: https://github.com/Database-Tycoon/tycoon-cli/issues/377
|
|
112
|
+
[#385]: https://github.com/Database-Tycoon/tycoon-cli/issues/385
|
|
113
|
+
[#387]: https://github.com/Database-Tycoon/tycoon-cli/issues/387
|
|
114
|
+
[#390]: https://github.com/Database-Tycoon/tycoon-cli/issues/390
|
|
115
|
+
[#439]: https://github.com/Database-Tycoon/tycoon-cli/issues/439
|
|
116
|
+
[#326]: https://github.com/Database-Tycoon/tycoon-cli/issues/326
|
|
117
|
+
|
|
3
118
|
## [0.2.3] - 2026-10-24
|
|
4
119
|
|
|
5
120
|
_Headline: **documentation site and a tested city**. The documentation site now publishes to GitHub Pages whenever a release reaches `main`, with internal pages withheld by a check that fails the build rather than leaking them. The city renderer is tested and gated in CI like the CLI, and its vehicles, guests and refresh now work. Also here: `tycoon-city` help that matches every other command, and tycoon's agent skills as three Claude Code plugins._
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: database-tycoon
|
|
3
|
-
Version: 0.2.
|
|
3
|
+
Version: 0.2.5
|
|
4
4
|
Summary: Tycoon CLI — local-first analytics CLI that adapts to your existing data stack
|
|
5
5
|
Project-URL: Homepage, https://github.com/Database-Tycoon/tycoon-cli
|
|
6
6
|
Project-URL: Repository, https://github.com/Database-Tycoon/tycoon-cli
|
|
@@ -20,7 +20,7 @@ Requires-Python: <3.14,>=3.12
|
|
|
20
20
|
Requires-Dist: dbt-core==1.12.0
|
|
21
21
|
Requires-Dist: dbt-duckdb==1.10.1
|
|
22
22
|
Requires-Dist: dlt[duckdb]==1.26.0
|
|
23
|
-
Requires-Dist: duckdb==1.5.
|
|
23
|
+
Requires-Dist: duckdb==1.5.4
|
|
24
24
|
Requires-Dist: httpx==0.28.1
|
|
25
25
|
Requires-Dist: pandas==3.0.3
|
|
26
26
|
Requires-Dist: pydantic==2.13.3
|
|
@@ -30,8 +30,10 @@ Requires-Dist: ruamel-yaml==0.19.1
|
|
|
30
30
|
Requires-Dist: sqlglot>=30.15.0
|
|
31
31
|
Requires-Dist: typer==0.27.0
|
|
32
32
|
Provides-Extra: docs
|
|
33
|
-
Requires-Dist: mkdocs-material==9.
|
|
33
|
+
Requires-Dist: mkdocs-material==9.8.1; extra == 'docs'
|
|
34
34
|
Requires-Dist: mkdocs==1.6.1; extra == 'docs'
|
|
35
|
+
Provides-Extra: motherduck
|
|
36
|
+
Requires-Dist: dlt[motherduck]==1.26.0; extra == 'motherduck'
|
|
35
37
|
Description-Content-Type: text/markdown
|
|
36
38
|
|
|
37
39
|
# tycoon
|
|
@@ -225,6 +227,8 @@ tycoon data query --db .tycoon/metadata.duckdb \
|
|
|
225
227
|
FROM dbt_runs ORDER BY started_at DESC LIMIT 10"
|
|
226
228
|
```
|
|
227
229
|
|
|
230
|
+
Add `--format csv` or `--format json` to get the rows alone, for a script or a notebook.
|
|
231
|
+
|
|
228
232
|
The metadata DB is disposable — delete `.tycoon/metadata.duckdb` to reset history.
|
|
229
233
|
|
|
230
234
|
## Contributing
|
|
@@ -235,5 +239,6 @@ outsized effect on where it goes. However you want to jump in:
|
|
|
235
239
|
- **Hit a bug or want a feature?** Open an [issue](https://github.com/Database-Tycoon/tycoon-cli/issues) — there's a short form for each.
|
|
236
240
|
- **Got a question, or want to show what you're building?** Start a [discussion](https://github.com/Database-Tycoon/tycoon-cli/discussions). Nothing's too small.
|
|
237
241
|
- **Want to work on the code?** [CONTRIBUTING.md](CONTRIBUTING.md) covers dev setup, what CI expects, and the repo conventions.
|
|
242
|
+
- **Wondering where tycoon is headed?** The [roadmap](https://database-tycoon.github.io/tycoon-cli/roadmap/) lists the current cycle, what comes next, and the wish list.
|
|
238
243
|
|
|
239
244
|
Everyone taking part is expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
|
|
@@ -189,6 +189,8 @@ tycoon data query --db .tycoon/metadata.duckdb \
|
|
|
189
189
|
FROM dbt_runs ORDER BY started_at DESC LIMIT 10"
|
|
190
190
|
```
|
|
191
191
|
|
|
192
|
+
Add `--format csv` or `--format json` to get the rows alone, for a script or a notebook.
|
|
193
|
+
|
|
192
194
|
The metadata DB is disposable — delete `.tycoon/metadata.duckdb` to reset history.
|
|
193
195
|
|
|
194
196
|
## Contributing
|
|
@@ -199,5 +201,6 @@ outsized effect on where it goes. However you want to jump in:
|
|
|
199
201
|
- **Hit a bug or want a feature?** Open an [issue](https://github.com/Database-Tycoon/tycoon-cli/issues) — there's a short form for each.
|
|
200
202
|
- **Got a question, or want to show what you're building?** Start a [discussion](https://github.com/Database-Tycoon/tycoon-cli/discussions). Nothing's too small.
|
|
201
203
|
- **Want to work on the code?** [CONTRIBUTING.md](CONTRIBUTING.md) covers dev setup, what CI expects, and the repo conventions.
|
|
204
|
+
- **Wondering where tycoon is headed?** The [roadmap](https://database-tycoon.github.io/tycoon-cli/roadmap/) lists the current cycle, what comes next, and the wish list.
|
|
202
205
|
|
|
203
206
|
Everyone taking part is expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
|
|
@@ -8,7 +8,7 @@ build-backend = "hatchling.build"
|
|
|
8
8
|
|
|
9
9
|
[project]
|
|
10
10
|
name = "database-tycoon"
|
|
11
|
-
version = "0.2.
|
|
11
|
+
version = "0.2.5"
|
|
12
12
|
description = "Tycoon CLI — local-first analytics CLI that adapts to your existing data stack"
|
|
13
13
|
readme = "README.md"
|
|
14
14
|
license = {text = "MIT"}
|
|
@@ -35,7 +35,7 @@ dependencies = [
|
|
|
35
35
|
# reader — tests/test_e2e_demo_arc.py fails without it. Optional-
|
|
36
36
|
# extra treatment tracked in #148.
|
|
37
37
|
"pandas==3.0.3",
|
|
38
|
-
"duckdb==1.5.
|
|
38
|
+
"duckdb==1.5.4",
|
|
39
39
|
"httpx==0.28.1",
|
|
40
40
|
"pyyaml==6.0.3",
|
|
41
41
|
"pydantic==2.13.3",
|
|
@@ -52,9 +52,12 @@ dependencies = [
|
|
|
52
52
|
]
|
|
53
53
|
|
|
54
54
|
[project.optional-dependencies]
|
|
55
|
+
motherduck = [
|
|
56
|
+
"dlt[motherduck]==1.26.0",
|
|
57
|
+
]
|
|
55
58
|
docs = [
|
|
56
59
|
"mkdocs==1.6.1",
|
|
57
|
-
"mkdocs-material==9.
|
|
60
|
+
"mkdocs-material==9.8.1",
|
|
58
61
|
]
|
|
59
62
|
|
|
60
63
|
[project.urls]
|
|
@@ -99,6 +102,11 @@ only-include = ["src", "pyproject.toml", "README.md", "LICENSE", "CHANGELOG.md",
|
|
|
99
102
|
packages = ["src/tycoon", "src/tycoon_city"]
|
|
100
103
|
|
|
101
104
|
[tool.uv]
|
|
105
|
+
# uv 0.12.22 is the first release that writes uv.lock at format revision 5;
|
|
106
|
+
# older releases write it back at revision 3 or lower, so a one-line dependency
|
|
107
|
+
# change becomes a format flip. setup-uv in CI reads this and installs the
|
|
108
|
+
# newest uv that satisfies it.
|
|
109
|
+
required-version = ">=0.12.22"
|
|
102
110
|
prerelease = "if-necessary-or-explicit"
|
|
103
111
|
|
|
104
112
|
[tool.pytest.ini_options]
|
|
@@ -2,8 +2,10 @@
|
|
|
2
2
|
|
|
3
3
|
from __future__ import annotations
|
|
4
4
|
|
|
5
|
+
from collections.abc import Callable
|
|
6
|
+
|
|
5
7
|
import typer
|
|
6
|
-
from typer.core import TyperGroup
|
|
8
|
+
from typer.core import TyperCommand, TyperGroup
|
|
7
9
|
|
|
8
10
|
import tycoon
|
|
9
11
|
|
|
@@ -14,6 +16,8 @@ _COMMAND_ORDER = [
|
|
|
14
16
|
"profiles",
|
|
15
17
|
"semantics",
|
|
16
18
|
"data",
|
|
19
|
+
"fire",
|
|
20
|
+
"firehouse",
|
|
17
21
|
"start",
|
|
18
22
|
"stop",
|
|
19
23
|
"city",
|
|
@@ -31,6 +35,8 @@ _SECTIONS = {
|
|
|
31
35
|
"profiles": "Project",
|
|
32
36
|
"semantics": "Project",
|
|
33
37
|
"data": "Data Pipeline",
|
|
38
|
+
"fire": "Fire & Response",
|
|
39
|
+
"firehouse": "Fire & Response",
|
|
34
40
|
"start": "Services",
|
|
35
41
|
"stop": "Services",
|
|
36
42
|
"city": "Services",
|
|
@@ -42,7 +48,31 @@ _SECTIONS = {
|
|
|
42
48
|
}
|
|
43
49
|
|
|
44
50
|
|
|
51
|
+
class _ProjectContext(typer.Context):
|
|
52
|
+
def invoke[T](self, callback: Callable[..., T], /, *args: object, **kwargs: object) -> T:
|
|
53
|
+
# Typer handles eager help before invocation. A group that delegates to
|
|
54
|
+
# a subcommand must wait for that subcommand to parse its own options.
|
|
55
|
+
if callback is self.command.callback and self.invoked_subcommand is None:
|
|
56
|
+
from tycoon.config import config
|
|
57
|
+
|
|
58
|
+
config.ensure_valid()
|
|
59
|
+
return super().invoke(callback, *args, **kwargs)
|
|
60
|
+
|
|
61
|
+
|
|
62
|
+
def _guard_project_commands(command: TyperCommand | TyperGroup) -> None:
|
|
63
|
+
command.context_class = _ProjectContext
|
|
64
|
+
if isinstance(command, TyperGroup):
|
|
65
|
+
for child in command.commands.values():
|
|
66
|
+
_guard_project_commands(child)
|
|
67
|
+
|
|
68
|
+
|
|
45
69
|
class _OrderedGroup(TyperGroup):
|
|
70
|
+
def __init__(self, **kwargs: object) -> None:
|
|
71
|
+
super().__init__(**kwargs)
|
|
72
|
+
for name, command in self.commands.items():
|
|
73
|
+
if name not in {"city", "docs", "doctor", "init", "run"}:
|
|
74
|
+
_guard_project_commands(command)
|
|
75
|
+
|
|
46
76
|
def list_commands(self, ctx: object) -> list[str]:
|
|
47
77
|
commands = super().list_commands(ctx)
|
|
48
78
|
return sorted(commands, key=lambda c: _COMMAND_ORDER.index(c) if c in _COMMAND_ORDER else 99)
|
|
@@ -90,13 +120,15 @@ def _root(
|
|
|
90
120
|
is_eager=True,
|
|
91
121
|
),
|
|
92
122
|
) -> None:
|
|
93
|
-
|
|
123
|
+
"""Run Database Tycoon commands."""
|
|
94
124
|
|
|
95
125
|
|
|
96
126
|
from tycoon.commands import data, profiles, register, semantics
|
|
97
127
|
from tycoon.commands import docs as docs_cmd_mod
|
|
98
128
|
from tycoon.commands.city import city_cmd
|
|
99
129
|
from tycoon.commands.doctor import doctor_cmd
|
|
130
|
+
from tycoon.commands.fire import fire as fire_cmd
|
|
131
|
+
from tycoon.commands.fire import firehouse as firehouse_cmd
|
|
100
132
|
from tycoon.commands.init import init_cmd
|
|
101
133
|
from tycoon.commands.notify import notify_cmd
|
|
102
134
|
from tycoon.commands.run import run_cmd
|
|
@@ -110,8 +142,10 @@ app.command(name="setup")(setup_cmd)
|
|
|
110
142
|
app.add_typer(register.app, name="register")
|
|
111
143
|
app.add_typer(profiles.app, name="profiles")
|
|
112
144
|
app.add_typer(semantics.app, name="semantics")
|
|
113
|
-
app.add_typer(data.app, name="data")
|
|
145
|
+
app.add_typer(data.app, name="data", no_args_is_help=True)
|
|
114
146
|
app.add_typer(docs_cmd_mod.app, name="docs")
|
|
147
|
+
app.command(name="fire")(fire_cmd)
|
|
148
|
+
app.command(name="firehouse")(firehouse_cmd)
|
|
115
149
|
app.command(name="start")(start_cmd)
|
|
116
150
|
app.command(name="stop")(stop_cmd)
|
|
117
151
|
app.command(name="city")(city_cmd)
|
|
@@ -25,7 +25,7 @@ from pathlib import Path
|
|
|
25
25
|
|
|
26
26
|
import typer
|
|
27
27
|
|
|
28
|
-
from tycoon.project import PROJECT_FILENAME
|
|
28
|
+
from tycoon.project import PROJECT_FILENAME, is_motherduck
|
|
29
29
|
from tycoon.utils.console import error, info
|
|
30
30
|
|
|
31
31
|
# The renderer ships in this wheel, so this line is for a broken install, not
|
|
@@ -35,10 +35,6 @@ _UNAVAILABLE = (
|
|
|
35
35
|
"city renderer unavailable ({error}) — this usually means a damaged install; try reinstalling database-tycoon"
|
|
36
36
|
)
|
|
37
37
|
|
|
38
|
-
# A MotherDuck catalog ("md:my_db", "md:_share/name/uuid") is a URI, not a
|
|
39
|
-
# filesystem path, and must reach the renderer untouched.
|
|
40
|
-
_MD_PREFIX = "md:"
|
|
41
|
-
|
|
42
38
|
|
|
43
39
|
def _project_root() -> Path:
|
|
44
40
|
"""Walk up from CWD to the directory holding tycoon.yml, else pyproject.toml."""
|
|
@@ -61,7 +57,8 @@ def _serve_target(path: str | None) -> str:
|
|
|
61
57
|
"""
|
|
62
58
|
if path is None:
|
|
63
59
|
return str(_project_root())
|
|
64
|
-
|
|
60
|
+
# A MotherDuck catalog is a URI, not a filesystem path, and must reach the renderer untouched.
|
|
61
|
+
if is_motherduck(path):
|
|
65
62
|
return path
|
|
66
63
|
return str(Path(path).resolve())
|
|
67
64
|
|
|
@@ -108,7 +105,9 @@ def city_cmd(
|
|
|
108
105
|
if pricing is not None:
|
|
109
106
|
argv += ["--pricing", str(pricing)]
|
|
110
107
|
|
|
111
|
-
|
|
108
|
+
# The query part of an md: string can carry motherduck_token; show the name only (gh-510).
|
|
109
|
+
shown = target.split("?", 1)[0] if is_motherduck(target) else target
|
|
110
|
+
info(f"Serving {shown} at http://{host}:{port} — Ctrl-C to stop.")
|
|
112
111
|
try:
|
|
113
112
|
code = serve(argv)
|
|
114
113
|
except KeyboardInterrupt:
|
|
@@ -9,17 +9,23 @@ app = typer.Typer(help="Data pipeline — sources, ingestion, transforms, and ex
|
|
|
9
9
|
|
|
10
10
|
def _register() -> None:
|
|
11
11
|
"""Wire sub-commands. Called once at import to avoid circular imports."""
|
|
12
|
-
from tycoon.commands import db, fivetran, history, observability, sources, transform
|
|
12
|
+
from tycoon.commands import db, fivetran, history, layers, observability, sources, transform
|
|
13
13
|
from tycoon.commands.explore import analyze_cmd
|
|
14
14
|
from tycoon.commands.run_all import run_all_cmd
|
|
15
|
+
from tycoon.commands.source_explorer import explore as explore_cmd
|
|
15
16
|
from tycoon.commands.status import status_cmd
|
|
16
17
|
from tycoon.commands.sync_cmd import sync_cmd
|
|
17
18
|
|
|
19
|
+
# `explore` rides inside the sources group (`tycoon data sources explore`)
|
|
20
|
+
# and `layers` is a plain command: a one-command sub-app would force the
|
|
21
|
+
# doubled `data layers layers` invocation.
|
|
22
|
+
sources.app.command(name="explore")(explore_cmd)
|
|
18
23
|
app.add_typer(sources.app, name="sources")
|
|
19
24
|
app.add_typer(transform.app, name="transform")
|
|
20
25
|
app.add_typer(history.app, name="history")
|
|
21
26
|
app.add_typer(observability.app, name="observability")
|
|
22
27
|
app.add_typer(fivetran.app, name="fivetran")
|
|
28
|
+
app.command(name="layers")(layers.layers)
|
|
23
29
|
app.command(name="query")(db.query)
|
|
24
30
|
app.command(name="schema")(db.schema)
|
|
25
31
|
app.command(name="clean")(db.clean)
|