Hadley Wickham
Hadley Wickham
And to link to our code review guidelines too.
Yeah, I think that's the best we can do since the syntax for named arguments varies so much across SQL dialects/functions.
Have you tried `df_sql %>% filter(col)`?
Hmmmm, exposing `.sql` is an interesting idea. We already have a way to force remote execution with `sql()` this would be more R CMD check friendly. I quite like the...
Given that `.env$mean(x)` clearly implies that we should evaluate `mean()` locally, I wonder if it's not too much of an abuse for `.data$mean(x)` to mean evaluate `mean(x)` in the database?...
I wonder if it would make sense to use `.sql$` internally too, to avoid the need for so many `globalVariables()`. OTOH it does make translations a little harder to read/understand.
Unfortunately `list_flatten()` is about as complicated as I want it to get. So unfortunately I don't think this is a good fit for purrr. But I appreciate the idea and...
@DavisVaughan does it have to? We added it to the upcoming dbplyr release.
Ok, makes sense.