[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: SERVER-4484 Comments attempting to describe how Cursors currently ensure consistency after a write
Branch: master
https://github.com/mongodb/mongo/commit/7775a2710b1455815e441edc0866260ea2964d26

Comment by auto [ 11/Mar/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-4669 SERVER-4484 Cursor::prepareToYield() no longer returns a value; Cursor::supportYields() should be checked before calling Cursor::prepareToYield() if yielding is required
Branch: master
https://github.com/mongodb/mongo/commit/8cf281eb779c7ebccd6c3b5b3783bef7e31c6893

Generated at Thu Feb 08 03:06:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.