Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-2222

notablescan mode neglects to fail some table scan queries

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Query Optimization

      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.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            aaron Aaron Staple
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: