Use option arrays for taking optional method arguments

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 1.0.0-beta2
    • Affects Version/s: 1.0.0-beta1
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, Collection and Database constructors, Client::selectDatabase(), and Database::selectCollection() all take their optional WriteConcern and ReadPreference arguments by position. Using an options array would be more flexible, consistent with our Operation classes (which take them as named options already), and not require users to remember which comes first.

            Assignee:
            Jeremy Mikola
            Reporter:
            Jeremy Mikola
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: