You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error message we get when we perform an unkeyed join now seems outdated:
When i is a data.table (or character vector), x must be keyed (i.e. sorted, and, marked as sorted) so data.table knows which columns to join to and take advantage of x being sorted. Call setkey(x,...) first, see ?setkey.
Since I solved my problem by simply adding on, and it seems that on is now generally the preferred approach for merges, should we not update this message?
The text was updated successfully, but these errors were encountered:
When i is a data.table (or character vector), data.table must know to which columns to join; this requires that either on is specified (see ?data.table) or x is keyed (i.e. sorted, and, marked as sorted, e.g. with setkey); there may be speed advantages if x is keyed and thus sorted.
Could also perhaps add a link to #1232 to the message, on, setkey, or some combination.
The error message we get when we perform an unkeyed join now seems outdated:
Since I solved my problem by simply adding
on
, and it seems thaton
is now generally the preferred approach for merges, should we not update this message?The text was updated successfully, but these errors were encountered: