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 7b79e4b
Browse filesBrowse the repository at this point in the historyBrowse files
refactor: move the execution history store into sqlbuild-python-front (#1543)
The execution history store (its SQLite and PostgreSQL backends, appends,
statements, conversions and Python functions) and the resource costs
table move from sqlbuild-python into sqlbuild-python-front, the layer
fensu already assigns them. Nothing in a lower crate imports them, so
the cost report can follow later without reaching back into
sqlbuild-python.
Old paths are deleted and callers updated; there are no re-exports. The
review command changes only its imports. main/ entries hold the bodies
they used to forward to. The resource costs table stays an XSB072/XSB073
edge as it was under native_host. The sqlbuild-python cap drops to its
new size, and the moved files' budgets are re-keyed with unchanged
totals.
Copy file name to clipboardExpand all lines: crates/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ tested and benchmarked with `cargo test` alone.
29
29
|`sqlbuild-project`| The compiled project as plain Rust: `CompiledProject` with the producers' facts and each resource's records (model inputs and schemas, compiled models and their analysis, sources, functions, audits and seeds), and what those records answer without Python, such as lineage rows, resolved namespaces and dependency keys. Values the host owns, such as user config and discovered files, and the views it builds lazily live in one slot per record, whose types `sqlbuild-python-project` supplies through the `ProjectHost` trait; reads that need Python stay in the bindings as extension traits. |
30
30
|`sqlbuild-cli`| The `sqb` and `sqlbuild` executables: `--version`, unchanged compiles replayed from the shared reuse store with Python's exact streams, exit code and compute log capture, and a handoff of every other invocation to the installed `sqlbuild-python` script. Built as its own wheel (`crates/sqlbuild-cli/pyproject.toml`). |
31
31
|`sqlbuild-python-base`| The base of the PyO3 bindings: native record, enum and error classes with their specs, registration, construction and field reads; keyword calls, imports, conversions and panics at the Python boundary; host entry calls; the process allocator; and the shared runtime the binding modules build on: the native store, compile context, diagnostics, progress and terminal text, warehouse access and orchestration reads. |
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. |
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, the warehouse state tables of consumption, observations and audit results, the execution history store and the resource costs table. |
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
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. |
0 commit comments