These are just the cases I've run into, possibly there are more:
t.find( {} );
- uses a table scan without generating an exception
t.find( ... );
- if the table is empty, no table scan exception is generated
t.count(
{a:1});
- seems to return 0 and not raise a js error (though last error appears to be set) - possibly this is just an issue with js count wrapper
Maybe we want to allow some of these cases, but if so we should document that fact.
- depends on
-
SERVER-2291 count command returns zero in some error cases rather than reporting an error with ok:false
- Closed
- is duplicated by
-
SERVER-3692 --notablescan doesn't prevent scans without a predicate
- Closed
-
SERVER-21302 Possible to run COLSCAN with --notablescan if there is no query specified
- Closed
- related to
-
SERVER-4327 allow dummy table scans in no table scan mode
- Closed