UpdateOp just looks for first match, even with multi updates

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      we could potentially choose the index based on more than the first match if we're doing a multi update (for example see how DeleteOp works)

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

              Created:
              Updated:
              Resolved: