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

feature: toggle whether to build tests for all columns or just primary keys #62

Open
Terroface opened this issue Sep 4, 2023 · 0 comments

Comments

@Terroface
Copy link
Collaborator

Terroface commented Sep 4, 2023

Being able to only generate tests for primary keys would allow large projects to use the dbt build statement without it being prohibitively slow.

This would likely sit in dbt_project.yaml

Being able to test_overwrite should still work in this case, as you might want to ensure you have specific tests for crucial non-pk columns even when you are using the newly envisaged pk-only test setting.

@Terroface Terroface changed the title feature: toggle whether to build tests for all columns or just unicity feature: toggle whether to build tests for all columns or just primary keys Sep 4, 2023
@Terroface Terroface changed the title feature: toggle whether to build tests for all columns or just primary keys feature: toggle whether to build tests for all columns or just primary keys Sep 4, 2023
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

1 participant