left.keyed handles conflicting columns artlessly.
Closed this issue · 2 comments
GoogleCodeExporter commented
For a left join e.g. x | y, the merge key is column intersection, whereas key
intersection might have been expected. If irrelevant columns are populated
inconsistently across x and y, they prevent the intended matches. Perhaps
another operator could be overloaded that merges on key intersection.
Alternatively, perhaps an operator with a left and right version (Dan P.
suggests <| and |> to indicate priority for columns not in the key).
Original issue reported on code.google.com by bergs...@gmail.com on 10 Jan 2013 at 2:12
GoogleCodeExporter commented
It seems risky to change the current behavior of the current operator. If
anything but the full intersection is used as the merge criterion, .x and .y
versions of columns may arise, disrupting the 'keyed' paradigm in unexpected
ways.
Original comment by bergs...@gmail.com on 5 Feb 2013 at 8:45
GoogleCodeExporter commented
Original comment by bergs...@gmail.com on 28 Mar 2013 at 2:58
- Changed state: WontFix