output from merge #4677

Activity

1. jangorecki

   added

   joinsUse label:"non-equi joins" for rolling, overlapping, and non-equi joinsUse label:"non-equi joins" for rolling, overlapping, and non-equi joins

   non-equi joinsrolling, overlapping, non-equi joinsrolling, overlapping, non-equi joins

   on Aug 26, 2020
2. jangorecki

   changed the title [-]feature request: output from merge[/-] [+]output from merge[/+] on Aug 26, 2020
3. jangorecki

   added

   feature request

   on Aug 26, 2020
4. ycphs

   added a commit that references this issue on Sep 22, 2020

   output from merge

   ...

   a206818
5. grantmcdermott commented on Dec 28, 2021

   

   grantmcdermott

   on Dec 28, 2021

   Contributor

   More actions

   I opened #5298 (now closed) before being flagged as a dup.

   Just to add that information about keys would be valuable too (see: #4888 and #4891).

   Also worth noting that the tidylog package largely provides this behaviour for dplyr joins.

   library(dplyr, warn.conflicts = FALSE)
   library(tidylog, warn.conflicts = FALSE)
   
   x = data.frame(A = 1:5, B = 6:10)
   y = data.frame(A = c(1, 4), C = LETTERS[c(1, 4)])
   
   left_join(x, y)
   #> Joining, by = "A"
   #> left_join: added one column (C)
   #>            > rows only in x   3
   #>            > rows only in y  (0)
   #>            > matched rows     2
   #>            >                 ===
   #>            > rows total       5
   #>   A  B    C
   #> 1 1  6    A
   #> 2 2  7 <NA>
   #> 3 3  8 <NA>
   #> 4 4  9    D
   #> 5 5 10 <NA>

   ^{Created on 2021-12-27 by the reprex package (v2.0.1)}

   👍React with 👍2Reacted by Thore Kockerols and Benjamin Schwendinger
6. MichaelChirico

   added

   top requestOne of our most-requested issuesOne of our most-requested issues

   on Apr 14, 2024