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.

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

Drop db_sql_render method? #46

Open
hadley opened this issue Sep 29, 2020 · 3 comments
Open

Drop db_sql_render method? #46

hadley opened this issue Sep 29, 2020 · 3 comments

Comments

@hadley
Copy link

hadley commented Sep 29, 2020

dbplyr now automatically drops ORDER BY from subqueries, so I don't think you need this any more, and I think you're the only user of the generic, which means I could (eventually) drop it from dbplyr.

@ianmcook
Copy link
Owner

ianmcook commented Sep 29, 2020

That's great; thanks for notifying me! I will plan to remove this method when I implement other changes soon to ensure continued compatibility with dbplyr .

@ianmcook
Copy link
Owner

Based on tidyverse/dbplyr#501, it looks like dbplyr now also issues a warning when it drops the ORDER BY in a subquery. This is great—thank you @hadley! Previously dbplyr did not issue a warning in this situation. In the specific case of Impala, I felt it was important to warn users when they used the arrange() verb in a way that would ultimately be ignored by Impala. Hence I made implyr detect this condition and issue a warning (but not actually drop the ORDER BY clause). I believe dbplyr now solves this whole problem upstream of implyr.

@hadley
Copy link
Author

hadley commented Sep 30, 2020

BTW I don't yet solve #30 (because it turns out that I fundamentally misunderstood the grammar for UNION and friends), but you're welcome to file it in dbplyr and I'll tackle it in a future release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants