When user tries to perform a command on a collection that doesn't exist then the mongo shell accepts it silently. In some cases that's fine. For example inserting a document creates a collection if it doesn't exist. However, there are other situations when it would be useful to get a warning about non-existing collection. Especially db.collection.update doesn't show any result and hence it's hard to distinguish if the command was correct (in terms of collection name).