tighten up semantics of Cursor interface

XMLWordPrintableJSON

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

      There are some subtle differences in the ways different cursors behave, for example some have matchers and some don't, some may change the return values of functions like indexKey() over the course of iteration, some may support certain operations when they are not ok() while others do not. We could simplify the behaviors, make them more uniform across cursors, and document them so users of the Cursor class know what to expect.

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

              Created:
              Updated:
              Resolved: