-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix distinct() for SQL sources #1942
Conversation
Current coverage is 61.68%@@ master #1942 diff @@
==========================================
Files 188 188
Lines 7459 7468 +9
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 4598 4607 +9
Misses 2861 2861
Partials 0 0
|
Would you mind adding a test for the SQL generation too? |
What do you have in mind -- something like the tests in test-sql-render.R? |
Yeah exactly - when reviewing this PR it would help if I had a concrete example of the SQL that is generated. |
Done. On second thought, |
Thanks - that seems like a reasonable approach to me. |
This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/ |
Without columns:
.keep_all
is ignored if no columns are selectedWith columns:
.keep_all = FALSE
is implemented using a grouped select.keep_all = TRUE
still raises an error, because DISTINCT syntax seems to vary between SQL dialectsAdapted tests.
Fixes #1937.