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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.6
    • Affects Version/s: None
    • Component/s: Shell
    • None
    • Fully Compatible
    • ALL
    • Quint Iteration 5, Quint Iteration 6
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Mathias Stearn
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: