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
non-equi join returning incorrect column name? #1807
Comments
This matches the behavior for rolling joins, so it's not new with non-equi joins:
It makes sense if you read Edit: By the way, when names overlap, you can use |
Ah yes, I see that now. That leads to the question as to whether it should do it this way? I see that from a |
This is a matter of being consistent to base R merge, related issue #1615. For base R it was not a problem as there was no non-equi merge. Before allowing |
The introduction of non-equi joins certainly brings the need to revisit this. Perhaps returning both x. and i. cols for non-equi joins (when used without |
Unless I'm missing smth, this is same as #1700, and imo non-equi joins just shine a bright light on this issue which has been bothering me since I started using rolling joins. I have to experiment with 2-3 combinations every time when using the rolling joins before I finally get the right one due to the confusing column naming. |
agree with @eantonya, closing as duplicate. |
When performing a non-equi join (in v1.9.7) on columns with different names, the returned column is given the name of the table on the left of the join, but contains values from the table on the right of the join - is this by design?
The text was updated successfully, but these errors were encountered: