[SERVER-395] Remove on a capped collection should fail before looking up what to remove Created: 28/Oct/09  Updated: 14/Jul/20  Resolved: 23/Nov/09

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.4

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

Participants:

 Description   

This came up because a remove on _id was being done, but these collections don't have an index on _id. It seems like having a remove error out before the lookup would be smarter. A person calling remove is already making one mistake by calling an illegal operation, so they are probably more likely to be calling it on _id or something else without an index.



 Comments   
Comment by auto [ 23/Nov/09 ]

Author:

{'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: fail fast on capped delete SERVER-395
http://github.com/mongodb/mongo/commit/4e9630f5d5b613050b9a040f665b534db81ffe03

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