coltrace 0.1.0.dev7__tar.gz → 0.1.0.dev8__tar.gz

{coltrace-0.1.0.dev7/src/coltrace.egg-info → coltrace-0.1.0.dev8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coltrace
-Version: 0.1.0.dev7
+Version: 0.1.0.dev8
 Summary: Static Pandas column lineage, impact analysis, and local dependency graphs
 Author: Cristiano Diniz
 License-Expression: MIT
@@ -32,7 +32,7 @@ column versions across direct function calls. Static scanning never imports or
 executes the project or reads its input data. Optional read capture observes
 column labels while you explicitly execute your own pipeline.
 
-**Development preview: `0.1.0.dev7`.** The supported subset is deliberately small.
+**Development preview: `0.1.0.dev8`.** The supported subset is deliberately small.
 Unsupported operations produce diagnostics and may interrupt lineage. A graph
 with no edge is not proof that a dependency does not exist.
 
@@ -58,10 +58,13 @@ separate release step; these commands install the local project.
 
 The source checkpoint recognizes supported SQL-to-Pandas and NoSQL-to-Pandas
 extractions. Literal SQL projections, aliases and expressions describe source
-fields before their first Python use. Query filters are control metadata rather
-than value dependencies of every output. The supplied
-`spark.sql(build_query(table)).toPandas()` pattern works with a resolved Spark
-session or an explicit source contract for an injected session.
+fields before their first Python use. Every database column the SQL reads is a
+selectable lineage node (`origin="table"`), so a column used only inside
+`SUM(...)` or a `WHERE` clause can be traced to the DataFrame columns it feeds.
+Query filters are control metadata rather than value dependencies of every
+output. `spark.sql(build_query(table)).toPandas()` keeps its SQL text even with
+an injected, unresolved session; SQL assembled from f-strings, `.format`, `%`
+and joins keeps its known text, with unknown parts shown as `{expression}`.
 
 `report.readers` inventories resolved `pd.read_*` calls with file, line, context,
 return shape and resulting DataFrame identity. File schemas are unknown unless
@@ -221,7 +224,7 @@ the shortest eligible distance, so a node reached both ways appears as direct.
 | --- | --- |
 | Explicit Pandas imports and aliases | Recognized origins; names such as `df` alone are insufficient |
 | Resolved `pd.read_*` calls | Located inventory; supported DataFrame readers plus explicit/observed source schemas; iterators/collections remain distinct |
-| SQL-to-Pandas extraction | Bounded SQL projections, aliases, expressions and helpers; documented readers/conversions or explicit contracts |
+| SQL-to-Pandas extraction | Bounded SQL projections, aliases, expressions and helpers; documented readers/conversions or explicit contracts; database columns as nodes; dialect fallback |
 | MongoDB / DynamoDB extraction | Literal projections and bounded Mongo expressions; candidate fields stay partial without observed schema |
 | Literal dictionary `DataFrame` construction | String column keys and literal values |
 | `frame["column"]`, `frame.loc[:, "column"]` | Literal or statically known labels (`for c in COLS`, f-strings) |
@@ -308,6 +311,8 @@ tox/nox and pytest/mypy/Ruff caches, `build`, and `dist`. Linked files/directori
 and Windows reparse points are skipped. A `.coltraceignore` file at the analyzed
 root uses gitignore syntax (root-level subset, including `!` negation). The root
 `.gitignore` is also applied unless `respect_gitignore = false` is set.
+`sql_dialect = "bigquery"` names the dialect of SQL text whose reader does not;
+text that does not parse is still retried in common dialects and reported.
 `observers = ["notify_team", "client.*"]` declares project helpers that only read
 the DataFrames they receive, so they do not interrupt lineage.
 `ScanConfig(exclude=("generated",))` overrides TOML settings and extends built-ins.