-
Notifications
You must be signed in to change notification settings - Fork 194
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
Please do not use using
#79
Conversation
I was gonna say, I thought this was always in the style guide! https://github.com/dbt-labs/corp/pull/58/files |
Co-authored-by: Brandon Thomson <brandon.thomson@dbtlabs.com>
@patkearns10 I thought it was as well ?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It definitely was! I believe it was removed when it was determined that Snowflake resolved the bugs around using
- that being said, I'm a-ok with being explicit about not using using
, since it is harder to comprehend, and can theoretically cause errors in multi-join CTEs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was meant to be an approval
We actually removed this explicitly when we reviewed the guide a few months back. I think that the initial comment was that there was performance reason with In my mind, |
This is my gripe with |
Add guidance to the style guide for writing explicit join instructions with an
on
clause instead of implicit join instructions with ausing
clause.The data team has experienced drift in our internal project based on personal preferences and would like to add this rule to the style guide to use for reference when we request changes on a
using
clause.