Dropping a non-existing collection does not return an error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.5
    • Affects Version/s: 2.5.5
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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"})

            Assignee:
            Eliot Horowitz (Inactive)
            Reporter:
            Christian Amor Kvalheim
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: