-
Notifications
You must be signed in to change notification settings - Fork 41
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
Adapt to the changes in dplyr 0.6.0 #76
Conversation
The changes: - Implement `db_desc` dispatching on `PrestoConnection`. - Some of the functions in dplyr moved to `dbplyr`. So we add a `dbplyr` compatibility function which pseudo-imports the function from the 'correct' package. This way we can provide backwards compatibility. - Update the tests to use 'quosures' and the new evaluation framework where necessary. resolves #75.
While this works with most types, it does not with `raw`. Either the current form, or: r <- as.raw(0) rq <- quo(r) ... as(a, !!rq) ... works.
@onurfiliz updated the pull request - view changes |
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.
Overall looks great, I'm a bit confused about one of the tests but o/w feel free to merge
l <- list(a=1L) | ||
expect_equal( | ||
translate_sql( | ||
as(x, !!l), |
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.
I'm confused about this line, why are we applying !!
to a list?
) | ||
expect_equal( | ||
translate_sql( | ||
as(x, !!local(list(a=Sys.time()))), |
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.
and here
Honestly I'm not sure why but these have to be |
The changes:
db_desc
dispatching onPrestoConnection
.dbplyr
. So we add adbplyr
compatibility function which pseudo-imports the function from the
'correct' package. This way we can provide backwards compatibility.
where necessary.
resolves #75.