Porting set operations from data frames to data tables: How to identify duplicated rows?

Duplicated.data. Table needs the same fix unique.data. Table got EDIT: Now done in v1.7.2.

Please raise another bug report: bug. Report(package="data. Table") For the benefit of others watching, you're already using v1.6.7 from R-Forge, not 1.6.6 on CRAN But, on Note 1, there's a 'not join' idiom : x-xy,which=TRUE See also FR#1384 (New 'not' and 'whichna' arguments?) to make that easier for users, and that links to the keys that don't match thread which goes into more detail.

Duplicated.data. Table needs the same fix unique.data. Table got EDIT: Now done in v1.7.2.

Please raise another bug report: bug. Report(package="data. Table").

For the benefit of others watching, you're already using v1.6.7 from R-Forge, not 1.6.6 on CRAN. But, on Note 1, there's a 'not join' idiom : x-xy,which=TRUE See also FR#1384 (New 'not' and 'whichna' arguments? ) to make that easier for users, and that links to the keys that don't match thread which goes into more detail.

Thanks! Good point - I forgot to mention that I've updated data.table. Also, bug.report() is new to me.

– Iterator Oct 19 at 14:46 Matthew, should your code be x-xy,which=TRUE, nomatch=0? Without the nomatch=0 argument I get this error: Error in . Default(xs, irows) : only 0's may be mixed with negative subscripts.

– RYogi Oct 27 at 3:46 @RYogi. Not sure. Need an example please, perhaps in a new question.

– Matthew Dowle Oct 27 at 8:39.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.