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

notablescan mode neglects to fail some table scan queries

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Querying
    • Query Optimization

    Description

      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.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            aaron Aaron Staple
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: