Some refactorings now that FLCS is less of a special case

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor - P4
    • WT10.0.1, 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None

      Now that FLCS supports timestamping and history, a number of things that previously needed to be different are the same for all the access methods and can be factored out or unified.

      Most notably, the 'When removing a key due to a tombstone with a durable timestamp of "none"' code is currently pasted three times and nearly all of it can be shared.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              David Holland
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: