cursorHandleFromId should verify that its not being called on a closed connection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.6.6, 4.0.0-rc0
    • Affects Version/s: None
    • Component/s: Shell
    • Fully Compatible
    • ALL
    • v3.6
    • Platforms 2018-05-07
    • 25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The old implementation of DBCommandCursor used when running the shell with --readMode compatibility calls getConnection(which checks if the connection has been closed) to construct a DBClientCursor which it passes to setCursor. The new variant used with --readMode command calls setCursorHandle with the cursor ID. This new variant doesn't check if the connection has been closed.

              Assignee:
              Mira Carey
              Reporter:
              Spencer Jackson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: