[JAVA-759] DBCollection.remove does not support justOne parameter Created: 15/Feb/13  Updated: 06/Apr/15  Resolved: 06/Apr/15

Status: Closed
Project: Java Driver
Component/s: API
Affects Version/s: 2.10.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alex Popiel Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

DBCollection.remove should optionally take a boolean parameter for the justOne flag. This change needs to be tunneled down into OutMessage, as well. Unfortunately, obvious workarounds (such as doing a find before the remove) introduce race conditions.



 Comments   
Comment by Jeffrey Yemin [ 06/Apr/15 ]

DBCollection is not going to get this, as it's been superseded by MongoCollection

Comment by Jeffrey Yemin [ 13/Mar/14 ]

This will be part of any new collection API, but not sure if we'll port it to DBCollection.

Comment by Jeffrey Yemin [ 25/Jun/13 ]

3.0.x branch supports this at a lower level. See https://github.com/mongodb/mongo-java-driver/blob/3.0.x/driver/src/main/org/mongodb/operation/protocol/DeleteMessage.java#L45.

But it's not surfaced in the MongoClient API yet.

Generated at Thu Feb 08 08:53:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.