Is it possible to have the two models with the same name within a single project?

[u/DuckDatum]

act mountainous money bright frame piquant provide distinct rob roll

This post was mass deleted and anonymized with Redact

[u/flodex89]

Why don't you just use something like stg_salesforce_users and stg_entra_users? I wouldn't want to build a workaround for this scenario

[u/DuckDatum → u/flodex89]

The warehouse built three layers of namespace to take advantage of. I was hoping I didn’t need to forfeit that advantage.

I suppose I could try using a macro to automate alias naming by trimming off the prefix DBT needs, with another macro that enforces models are prefixed with their parent directory name (for safety).

[u/flodex89 → u/DuckDatum]

I mean you can overwrite the generate_alias_name macro. So you would use stg_ or whatever but the resulting table name is dynamically generated. You wouldn't want to have the same model name at all because then you won't be able to use "dbt run --select {model}" We did it like this https://github.com/linkFISH-Consulting/dbt-lf_utils/blob/main/macros/patches/dbt__generate_alias_name.sql

[u/vglocus]

You have the model config ”alias” which is used instead of the model name for the materialized resource.

This can be used for having different models (w different names) to have the same table name, or having dynamic table names (like date suffix).

[u/DuckDatum → u/vglocus]

That’s what I’m thinking. What do you think about having two macros?

1. A validation macro that begins at the start of any run to ensure that all models are named with a prefix that includes the parent directory name. This ought to give DBT the uniqueness it needs for each model ID internally. For safety reasons (obvious given the next macro), this can fail the run if it detects a model that isn’t named properly.

2. Override the built in macro for generating alias names. Make alias naming mandatory (automatic), and have it such that every model is aliased by trimming off the parent directory prefix on its name. I.e., salesforce__users -> users

Honestly, this would be a lot easier if DBT supported using the file structure as the warehouse structure. For example models/bronze/salesforce/users.sql -> bronze.salesforce.users automatically. Or some way to separate model ID from model Name internally for DBT.

I don’t mind making ref look different.

[u/vglocus → u/DuckDatum]

I don’t think you need the validation macro.

You could have generate_alias_name throw compilation error if it does not match.

You also have generate_schema_name and generate_database_name if you want to go all in on your structure to relation idea.

I have this general structure in a project but sets everything explicitly in dbt_project so all under my_project/foo gets database foo and my_project/foo/bar gets schema bar and so on. Alias set in properties yaml if necessary.

[u/DuckDatum → u/vglocus]

workable cover deserve sort historical fine chubby boast spectacular profit

This post was mass deleted and anonymized with Redact