-
Type: New Feature
-
Resolution: Won't Fix
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage Execution
Some users have asked whether the we could record the inverse of what's in the oplog, in order to perform roll-backward operations (e.g., record the values that get overwritten on updates).
Obviously, this sort of thing gets hard/impractical in the presence of collection/database dropping, but even if the undos only went back to an empty collection/db, it could be useful for some problems.
- is duplicated by
-
SERVER-8726 oplog record the old data when op is update or delete
- Closed