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 0fe0645
Browse filesBrowse the repository at this point in the historyBrowse files
Fix!: do not apply model_defaults statements to external models
External models inherited the model_defaults pre_statements, post_statements
and on_virtual_update, but are built without the project's macros and never
execute statements. When a default statement called a project macro and its
text changed, the plan rendered the external model's statements to compare
them and failed with "Macro '<name>' does not exist".
Stop external models from inheriting these defaults, as is already done for
the default gateway. This changes the fingerprint of external models in
projects that use default statements; the empty migration bumps the state
schema version so cached models are rebuilt.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Simen Strand <simen.strand@netcheck.de>
Copy file name to clipboardExpand all lines: docs/reference/model_configuration.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
@@ -136,7 +136,7 @@ You can also use the `@model_kind_name` variable to fine-tune control over `phys
136
136
)
137
137
```
138
138
139
-
You can aso define `pre_statements`, `post_statements` and `on_virtual_update` statements at the project level that will be applied to all models. These default statements are merged with any model-specific statements, with default statements executing first, followed by model-specific statements.
139
+
You can aso define `pre_statements`, `post_statements` and `on_virtual_update` statements at the project level that will be applied to all models except [external models](../concepts/models/external_models.md). These default statements are merged with any model-specific statements, with default statements executing first, followed by model-specific statements.
0 commit comments