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

Jump to bottom

Please do not use using #79

Merged
merged 2 commits into from
Feb 8, 2023
Merged

Please do not use using #79

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f7aca02
Please do not use
Feb 8, 2023
08c3799
Update dbt_style_guide.md
epapineau Feb 8, 2023
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: 2 additions & 0 deletions dbt_style_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,6 +283,8 @@ For more information about why we use so many CTEs, check out [this glossary ent

- Be explicit about your join (i.e. write `inner join` instead of `join`). `left joins` are the most common, `right joins` often indicate that you should change which table you select `from` and which one you `join` to.

- Avoid the `using` clause in joins, preferring instead to explicitly list the CTEs and associated join keys with an `on` clause.

- Joins should list the left table first (i.e., the table you're joining data to)
Example:
```sql
Expand Down