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
Currently, all stg and int models are materialized in the database. This clutters the schema and is not desirable for production analytic use cases. However, developers (and analysts in some cases) may want/need to inspect the contents of these models.
We can use a dbt_project variable that users pass into the command line that will enable materialization of stg and int models (I think it should be disabled by default).
The text was updated successfully, but these errors were encountered:
Currently, all stg and int models are materialized in the database. This clutters the schema and is not desirable for production analytic use cases. However, developers (and analysts in some cases) may want/need to inspect the contents of these models.
We can use a dbt_project variable that users pass into the command line that will enable materialization of stg and int models (I think it should be disabled by default).
The text was updated successfully, but these errors were encountered: