-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Cursors, Layered Tables
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - 2025-10-10
-
3
Currently that's defined only for search, search_near, prev and next. But we also expect modify, update and remove to return positioned cursors, while insert should always return the cursor unpositioned.
It's worth adding this info to the docs on this page: https://source.wiredtiger.com/develop/cursor_ops.html
- related to
-
WT-14684 Disagg testing: add PALite, an alternative PALI mock implementation that uses SQLite
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
WT-15408 Fix prepare insert rollback with an onpage value that has a globally visible stop time point
-
- Closed
-