-
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
Some (?) interactions between select
and window functions result in error (dbplyr 2.3.0)
#1104
Comments
Thanks for the reprex! By the way you should use |
Yeah, by now we maintain our own R package, which dynamically creates dplyr queries, and in the end using your cool dbplyr package to generate and send off a final SQL to gather data for some reporting purposes. So the queries can become quite massive and convoluted at times. Unfortunately I will not be able to test this until next Monday, but then I will provide feedback. Thanks for the hint! I was actually using |
Ah, that sounds interesting. So you might benefit a lot from the 2.3 version as the reduced number of subqueries for joins can lead to big performance gains (at least I had a couple of cases already). Yes, the PR includes the fix for the 4 table join bug. |
That why I was eager to test the new version. :) I tested the PR and I can confirm that it fixes the issue, thank you! |
Hi,
I think I found another regression in dbplyr 2.3.0.
It is quite an artifical example, but nevertheless. An explicit selection after a summarizing operation seems to somehow result in problems when using window functions afterwards. (In this example we see
row_number()
, but I also have the problem withslice_*()
).Created on 2023-01-19 with reprex v2.0.2
Removing the intermediate
select
statement makes it work correctly. (Of course in this example theselect
is superfluous anyways, but in my actual query it is not.)Created on 2023-01-19 with reprex v2.0.2
The text was updated successfully, but these errors were encountered: