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

DBCommandCursor::next() shell method shouldn't require calling hasNext first

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.1.6
    • None
    • Shell
    • None
    • Fully Compatible
    • ALL
    • Quint Iteration 5, Quint Iteration 6

    Description

      In the current interface between the shell and the c++ driver, hasNext() is what fetches the results from the server if at the end of the current batch. next() just reads from the current batch. DBQuery smooths over this weirdness by calling hasNext() from next() and throwing if it returns false. DBCommandCursor should do the same.

      Attachments

        Activity

          People

            mathias@mongodb.com Mathias Stearn
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: