TimestampOperations::MergeMember() needs to make a predictable choise when the timestamps don't differ. The suggested solution is to look at the member data.
--- old+++ new@@ -1 +1 @@-TimestampOperations::MergeMember?() needs to make a predictable choise when the timestamps don't differ. The suggested solution is to look at the member data. +TimestampOperations::MergeMember() needs to make a predictable choise when the timestamps don't differ. The suggested solution is to look at the member data.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
//TODO:thiswholeoperationshouldberewrittentoworkdirectlyonblobs.//Todothisweneedtoexporttheblob-operationsthatcancauseblobreallocations//indots_kernelsothatthey're usable from dots_cpp (and other languages??)//TODO:needtolookatdatatoo!!!!//changeflagmustonlybesetinmergeresultifthedatadiffers!//TODO:handlethe=casebylookingatthememberdata!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Diff:
Some TODOs from TimestampOperations::MergeMember
TODO from TimestampOperations::Merge:
TODO from HaveChanges: