We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Submitted by: Matt Dowle; Assigned to: Nobody; R-Forge link
Use matching column names in this case.
As suggested by David Kulp here :
http://lists.r-forge.r-project.org/pipermail/datatable-help/2012-August/001241.html
Or, leave this to merge (since merge.data.table does that)? And if so, document.
The text was updated successfully, but these errors were encountered:
This is easy now with on, correct? could set default of on to intersect(names(dt1),names(dt2)), for example.
on
intersect(names(dt1),names(dt2))
Sorry, something went wrong.
@MichaelChirico I would prefer to see a special value for on (similar to .EACHI), to keep it explicit/transparent, like on=.COMMON.
.EACHI
on=.COMMON
While we're at it, I suppose there could be an onby (if the logic & code are structured so that that actually makes sense).
onby
This seems like a close relative of the recently-closed #1517
@franknarf1 in keeping with SQL-inspired syntax, I was thinking on = .NATURAL would be a very natural (sorry) way to implement this.
on = .NATURAL
add natural join support, closes #629
de61845
add natural join support, closes #629 (#3571)
6484781
Successfully merging a pull request may close this issue.
Submitted by: Matt Dowle; Assigned to: Nobody; R-Forge link
Use matching column names in this case.
As suggested by David Kulp here :
http://lists.r-forge.r-project.org/pipermail/datatable-help/2012-August/001241.html
Or, leave this to merge (since merge.data.table does that)? And if so, document.
The text was updated successfully, but these errors were encountered: