Add a diagnostic check for updates to the same key out of timestamp order

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.3, 3.7.2, WT3.1.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2017-12-04, Storage 2017-12-18, Storage 2018-01-01, Storage 2018-01-15
    • None

      The documentation in docs/transactions.dox states:

      The commits to a particular data item must be performed in timestamp order.
      Again, this is only checked in diagnostic builds and if applications violate
      this rule, data consistency can be violated.
      

      I attach a simple python unit test that illustrates this is not being checked in a diagnostic build.

      The code should be brought in line with the documentation.

              Assignee:
              Susan LoVerso (Inactive)
              Reporter:
              Susan LoVerso (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: