You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7f9ba65
Browse filesBrowse the repository at this point in the historyBrowse files
refactor: move the compile layer of the Python bindings into sqlbuild-python-compile
sqlbuild-python is still over the crate size limit. The compile layer
(compile command and driver, input loops, compile-input attachment,
project assembly, analysis and the analysis session, Rules, lineage,
semantic checks, compile deltas and outputs, the DAG artifact, manifest,
frontier, offline scope facts, SQL test glue and auditing) moves into a
new crate above sqlbuild-python-project and beside
sqlbuild-python-planner. Neither depends on the other. Command handlers
that also reach the planner stay in sqlbuild-python.
Old paths are deleted and callers updated; there are no re-exports.
main/ entries hold the bodies they used to forward to, except 13 whose
bodies are over the entry size budgets. The sqlbuild-python cap drops
to its new size, XSB072/XSB073 budgets are re-keyed with unchanged
totals, and the native field fallback list and compiler-differential
scan paths follow the moved files.
Copy file name to clipboardExpand all lines: crates/README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,14 +32,15 @@ tested and benchmarked with `cargo test` alone.
32
32
|`sqlbuild-python-front`| The front of the compile pipeline as PyO3 bindings, on top of `sqlbuild-python-base`: project discovery, model configuration and headers, scopes, macro rendering and authored values, SQL text, model attachment and the compile driver, cursors, contract and refactor facts, and the warehouse state tables of consumption, observations and audit results. |
33
33
|`sqlbuild-python-project`| The compiled project as PyO3 bindings, on top of `sqlbuild-python-front`: the project host and the Python views of compiled models, inputs and resources, the compiled-project snapshot, analysis classes and the analysis session, the project graph, references, lineage, fingerprints, contracts and semantic shapes, audit rendering, and the planner's identities, scope, selection, phases, fixture strategy and SQL test planning. |
34
34
|`sqlbuild-python-planner`| The plan layer as PyO3 bindings, on top of `sqlbuild-python-project`: execution plans and their entries, planner phases, change detection, migrations, reference and cursor resolution, scenarios, strategy and warehouse inspection, plus freshness, consumption, microbatches, observations, lifecycle events and plan output. |
35
-
|`sqlbuild-python`| The `_native` module: its Python classes and functions and the conversions from Python objects, on top of `sqlbuild-python-planner`, `sqlbuild-python-project`, `sqlbuild-python-front` and `sqlbuild-python-base`. |
35
+
|`sqlbuild-python-compile`| The compile layer as PyO3 bindings, on top of `sqlbuild-python-project` and beside `sqlbuild-python-planner`: the compile command and driver, input loops and compile-input attachment, project assembly, analysis and the analysis session, Rules, lineage, semantic checks, compile deltas and outputs, the DAG artifact, manifest, frontier, offline scope facts, SQL test glue and auditing. |
36
+
|`sqlbuild-python`| The `_native` module: its Python classes and functions and the conversions from Python objects, on top of `sqlbuild-python-compile`, `sqlbuild-python-planner`, `sqlbuild-python-project`, `sqlbuild-python-front` and `sqlbuild-python-base`. |
36
37
37
38
## Layering
38
39
39
40
Dependencies point one way, from the top of this graph to the bottom:
description = "The compile layer of the sqlbuild._native bindings: the compile driver and command, input loops, project assembly, analysis and the analysis session, rules, lineage, semantic checks, compile deltas and outputs, the DAG artifact, manifest, frontier and auditing."
0 commit comments