-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
5
The WT_CURSOR::modify API is a bit unusual, in that an update chain will build upon previous entries to create a full version of a value. We should add testing to ensure that WT_CURSOR::modify works as expected when used with unusual timestamp rules. Including if interleaving timestamp and non-timestamped updates, and adding timestamped updates out of order.
This is follow on from WT-4776
- is related to
-
WT-4776 Modify operations should be equivalent to updates
- Closed