Remove on a capped collection should fail before looking up what to remove

XMLWordPrintableJSON

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

      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.

              Assignee:
              Eliot Horowitz (Inactive)
              Reporter:
              jeff jenkins
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: