Details
-
Improvement
-
Resolution: Fixed
-
Major
-
feature-backlog
-
Security Level: Public
-
None
-
ForestDB: Oct 26 - Nov 13
Description
In some applications, clients just want to know if there have been any changes in a given KV store since its last check. This can be easily supported by maintaining a sequence number counter for each KV instance, but it doesn't need to assign a unique sequence number to each mutated doc and maintain a sequence tree.
Attachments
| For Gerrit Dashboard: MB-13814 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 47937,2 | MB-13814 Provide sequence number even for DB without seq-tree | sherlock | forestdb | Status: MERGED | +2 | +1 |
| 47979,1 | Merge remote-tracking branch 'origin/sherlock' | master | forestdb | Status: MERGED | +2 | +1 |