[SERVER-4203] return an error if a find is issued against a collection that does not exist Created: 03/Nov/11  Updated: 16/Nov/11  Resolved: 04/Nov/11

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

Type: Improvement Priority: Major - P3
Reporter: Chris Westin Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I often hear complaints about queries not working, when we're just returning nothing because the target collection doesn't exist. This can happen because of a typo in the collection name, or because an attempt to do the query in the wrong database (i.e., the collection is in another database).



 Comments   
Comment by Chris Westin [ 16/Nov/11 ]

I've heard so many complaints about this, and about accidentally sending documents off into unknown collections (due to typos in new application code), that I don't think anyone will mind this change. They ask for it to help them avoid making these mistakes.

Comment by Eliot Horowitz (Inactive) [ 04/Nov/11 ]

This totally changes the semantics.

Wouldn't do this unless in a strict mode.

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