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
I recently upgraded to 1.9.2 and encountered the following issue. Previously this returned an empty data.table as I had expected (and desired), but now returns an error:
x<- data.table(a=character(0), b=character(0), c=numeric(0))
setkey(x, a, b)
x[J("foo", character(0)), nomatch=0]
Errorinif (mn%%n[i] !=0) warning("Item ", i, " is of size ", n[i], :missingvaluewhereTRUE/FALSEneededx[J(character(0), "foo"),nomatch=0]
Errorinif (mn%%n[i] !=0) warning("Item ", i, " is of size ", n[i], :missingvaluewhereTRUE/FALSEneeded
if there is only one key then this seems to behave as before
is this expected with the new release? in my actual usage character(0) is a value held by another variable and that variable is used to search inside the data.table - is it user's responsibility to now check and avoid searching with empty character vectors?
The text was updated successfully, but these errors were encountered:
I recently upgraded to 1.9.2 and encountered the following issue. Previously this returned an empty data.table as I had expected (and desired), but now returns an error:
if there is only one key then this seems to behave as before
is this expected with the new release? in my actual usage
character(0)
is a value held by another variable and that variable is used to search inside thedata.table
- is it user's responsibility to now check and avoid searching with empty character vectors?The text was updated successfully, but these errors were encountered: