Menu

#48 Predictable merge when timestamps don't differ

Unplanned
new
nobody
From Trac (2)
bug
dose
2015-04-27
2012-10-30
No

TimestampOperations::MergeMember() needs to make a predictable choise when the timestamps don't differ. The suggested solution is to look at the member data.

Discussion

  • Lars Hagström

    Lars Hagström - 2012-10-30
    • Description has changed:

    Diff:

    --- 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. 
    
     
  • Lars Hagström

    Lars Hagström - 2015-04-27

    Some TODOs from TimestampOperations::MergeMember

    //TODO: this whole operation should be rewritten to work directly on blobs.
    //To do this we need to export the blob-operations that can cause blob reallocations
    //in dots_kernel so that they're usable from dots_cpp (and other languages??)
    
    //TODO: need to look at data too!!!!
    //change flag must only be set in merge result if the data differs!
    
    //TODO: handle the = case by looking at the member data!
    
     
  • Lars Hagström

    Lars Hagström - 2015-04-27

    TODO from TimestampOperations::Merge:

    //TODO: optimize this!
    
     
  • Lars Hagström

    Lars Hagström - 2015-04-27

    TODO from HaveChanges:

            //TODO: handle the == case. look at member data!
    
     
MongoDB Logo MongoDB