[SERVER-6] cursors can return the same object twice Created: 09/Apr/09  Updated: 04/Apr/23  Resolved: 26/May/09

Status: Closed
Project: Core Server
Component/s: Usability
Affects Version/s: 0.9.3
Fix Version/s: 0.9.3

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

If an object is updated while another client is traversing a cursor, it can move later in the collection and then a cursor might return it a second time.

the babble driver did auto deduping by id itself. we should at this point do something db-side to handle.



 Comments   
Comment by Githook User [ 23/Feb/22 ]

Author:

{'name': 'Dylan Richardson', 'email': 'Dylan@Neatmaps.com', 'username': 'dylrich'}

Message: BUILD-14689: add server-6.0 public pgp keys
Branch: master
https://github.com/10gen/mongodb-www/commit/00037e35959fc94a35f6a6708b1bdc59b5c702bc

Comment by Aaron Staple [ 11/May/09 ]

Ok, I implemented this. Tested in cursortests.cpp and norepeat.js.

Generated at Thu Feb 08 02:52:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.