add an explicit requireOrder argument to NamespaceDetailsTransient::getCursor()

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 2.1.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The following assumption makes it difficult for NamespaceDetailsTransient::getCursor() to be used for index only projection by clients other than the query implementation.

              /** If no ParsedQuery was supplied, it's assumed no reordering will be applied. */
              bool requireOrder() const { return !_parsedQuery; }
      

      It is straightforward to replace this with an additional argument to NamespaceDetailsTransient::getCursor().

              Assignee:
              Aaron Staple (Inactive)
              Reporter:
              Aaron Staple (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: