-
Notifications
You must be signed in to change notification settings - Fork 178
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
Use LHS.*
after left_join()
#959
Conversation
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.
Looks great!
NEWS.md
Outdated
@@ -1,5 +1,8 @@ | |||
# dbplyr (development version) | |||
|
|||
* When possible, dbplyr now uses `SELECT *` after a left join instead of |
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.
Or inner join?
Could we apply the same logic to right joins too?
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.
Not that simple to extend this to all type of joins but now they are all supported (note that for full_join()
one can never use *
).
tests/testthat/_snaps/verb-expand.md
Outdated
@@ -4,7 +4,7 @@ | |||
lazy_frame(x = 1, y = 1) %>% tidyr::expand(x, y) | |||
Output | |||
<SQL> | |||
SELECT `x`, `y` | |||
SELECT `LHS`.*, `RHS`.* |
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.
If it's easy, maybe we should only use *
if there is more than one variable selected?
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.
Yes, this looks a bit better now.
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.
Nice!
Closes #898. There should be no issues with Oracle this time as this uses a table alias.
Created on 2022-08-04 by the reprex package (v2.0.1)