Use insertion-ordered map in ops.Find

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Because `collection.FindOne()` allows the user to specify FindOptions, it's possible that a user could specify a limit other than 1. To ensure that the command has the correct semantics, we should change ops.Find to use an insertion-ordered map once it's implemented instead of a bson.D and ensure that the last option in the list has precedence.

            Assignee:
            Samuel Rossi (Inactive)
            Reporter:
            Samuel Rossi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: