[SERVER-12290] Dropping a non-existing collection does not return an error Created: 08/Jan/14  Updated: 11/Jul/16  Resolved: 10/Jan/14

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

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

Operating System: ALL
Participants:

 Description   

Dropping a non existing collection with the drop command returns a namespace error in pre 2.5.5 but no error in 2.5.5

db.runCommand({drop:"doesnotexist"})



 Comments   
Comment by Githook User [ 10/Jan/14 ]

Author:

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

Message: SERVER-12290: fix dropping non-existant collection error
Branch: master
https://github.com/mongodb/mongo/commit/0815ed104abdca1c7443c641ab2b0eade0c776fd

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