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

top-level config scope #161

Closed
jthandy opened this issue Sep 23, 2016 · 1 comment
Closed

top-level config scope #161

jthandy opened this issue Sep 23, 2016 · 1 comment
Assignees
Milestone

Comments

@jthandy
Copy link
Member

jthandy commented Sep 23, 2016

tristan [1:01]
is it possible to create a configuration at the level of models:

[1:01]
so that it would be across all models, not just within a specific package?

[1:01]
that's the ideal place to put the pre-hook and post-hook for audit tables.

drew [1:03 PM]
yeah, i was thinking about that too! Not currently possible, but it’s a good idea and shouldn’t be super tricky to implement

[1:03]
kind of like our model-defaults from earlier

tristan [1:03 PM]
yes, but not some separate dumb thing.

@drewbanin drewbanin modified the milestone: 0.5.1 Release Sep 28, 2016
@drewbanin drewbanin self-assigned this Sep 28, 2016
@drewbanin
Copy link
Contributor

0.5.1 release

yu-iskw pushed a commit to yu-iskw/dbt that referenced this issue Aug 17, 2021
…ips_where

Add a new schema test: relationships_where
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants