-
Type: Task
-
Resolution: Done
-
None
-
Affects Version/s: None
-
Component/s: 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?
- is related to
-
WT-296 non-transactional objects
- Closed