support for non-transactional objects.

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None

      Michael, what's the plan for mixing and matching transactional operations with non-transactional operations?

      For example, test/suite/test_txn02.py inserts two records, but then performs transactions on the objects. That's safe now with checkpoint durability, but won't be safe when we offer finer-grained durability and we're recovering from log records.

      Should this be an error now, and if so, where/how do you want to detect it?

              Assignee:
              Unassigned
              Reporter:
              Keith Bostic (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: