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.

Sign up for GitHub

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

Remove link to customizing the name of a model's database identifier using the alias model config #6610

Merged
merged 2 commits into from
Dec 9, 2024
Merged

Remove link to customizing the name of a model's database identifier using the alias model config #6610

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cea0849
Remove link to customizing the name of a model's database identifier
dbeatty10 Dec 6, 2024
8f5fff8
Merge branch 'current' into dbeatty10-patch-1
mirnawong1 Dec 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/docs/build/unit-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ Starting in dbt Core v1.8, we have introduced an additional type of test to dbt
- We currently _don't_ support unit testing models that use recursive SQL.
- If your model has multiple versions, by default the unit test will run on *all* versions of your model. Read [unit testing versioned models](/reference/resource-properties/unit-testing-versions) for more information.
- Unit tests must be defined in a YML file in your [`models/` directory](/reference/project-configs/model-paths).
- Table names must be [aliased](/docs/build/custom-aliases) in order to unit test `join` logic.
- Table names must be aliased in order to unit test `join` logic.
- Include all [`ref`](/reference/dbt-jinja-functions/ref) or [`source`](/reference/dbt-jinja-functions/source) model references in the unit test configuration as `input`s to avoid "node not found" errors during compilation.

#### Adapter-specific caveats
Expand Down
Loading