Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add real example of customizing generate_schema_name() and generate_database_name() for common use cases #4318

Open
1 task done
b-per opened this issue Oct 24, 2023 · 0 comments
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@b-per
Copy link
Contributor

b-per commented Oct 24, 2023

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/docs/build/custom-schemas
https://docs.getdbt.com/docs/build/custom-databases
https://docs.getdbt.com/docs/build/custom-aliases

What part(s) of the page would you like to see updated?

The pages are currently described separately and explain the concepts but they don't "bring it all together" to real use cases. Many people have questions about those macros and don't really know how to use them.

My idea would be to bring it all together and provide examples of those macros based on "database/schema" design chose by a company. Something like:

Typical Use case generate_database_name() generate_schema_name() generate_alias_name()
(default) One schema per developer Custom schemas concatenated to the target schema
One schema per developer Custom schemas not concatenated to the target schema in Prod Custom schemas concatenated in Dev (write example)
One single schema for all developers Separating developers objects by adding user name to the table (write example) (write example)
One database per developer (write example) (write example)

Additional information

No response

@b-per b-per added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

No branches or pull requests

1 participant