[SERVER-4484] tighten up semantics of Cursor interface Created: 13/Dec/11 Updated: 10/Dec/14 Resolved: 14/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
There are some subtle differences in the ways different cursors behave, for example some have matchers and some don't, some may change the return values of functions like indexKey() over the course of iteration, some may support certain operations when they are not ok() while others do not. We could simplify the behaviors, make them more uniform across cursors, and document them so users of the Cursor class know what to expect. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 14/Jan/14 ] |
|
The Cursor interface has gone away |
| Comment by auto [ 23/Mar/12 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by auto [ 11/Mar/12 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |