dbcursor.count() should update based on limit() and skip()

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Won't Fix
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Shell
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After retrieving a cursor from a query, calling count() on it always returns the total number of matching records, even after calling limit() or skip() on it. It would be nice if count() was updated to reflect the number of matching records after any cursor manipulation with limit() and skip().

      This would ideally be a universal change for the various drivers as well to maintain consistent behavior, but I did not create issues specifically for each of them. Perhaps if this is accepted, that kind of change could be considered.

            Assignee:
            Eliot Horowitz (Inactive)
            Reporter:
            Liam Staskawicz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: