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
This could be useful when paired with custom schemas. For example, there could be a users table in both the snowplow_analytics and product_analytics schemas. Behind these scenes, these models would be named something like snowplow_users.sql and product_users.sql, respectively.
👍 This would be tremendously helpful when migrating to dbt so as to ensure parity with existing data infrastructures that were not built with dbt in mind.
This could be useful when paired with custom schemas. For example, there could be a
users
table in both thesnowplow_analytics
andproduct_analytics
schemas. Behind these scenes, these models would be named something likesnowplow_users.sql
andproduct_users.sql
, respectively.Config would look like:
dbt would need to enforce uniqueness between
schema + aliased_name
The text was updated successfully, but these errors were encountered: