error when dropping a collection that does not exist

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • 3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Please refer to the following mailing list thread for the discussion on this issue:
      https://groups.google.com/group/mongoid/browse_thread/thread/16baf2f415d8a905

      Dropping a collection that has a definition but does not exist in the database currently returns an error in Mongoid 3.0, it should return false instead. For instance:

         MongoUser.collection.drop

      Should return

      • true if the collection exists and it was dropped
      • false if the collection does not exist.

              Assignee:
              Unassigned
              Reporter:
              digitalplaywright
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: