notablescan mode neglects to fail some table scan queries

XMLWordPrintableJSON

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

      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:
              [DO NOT USE] Backlog - Query Optimization
              Reporter:
              Aaron Staple (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: