Split ClientUpdateOptions and ClientDeleteOptions into operation-specific classes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Java Drivers
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Following updates in bulk write specification that introduce a sort option applicable to updateOne but not updateMany, we should restructure ClientUpdateOptions and ClientDeleteOptions. This restructuring will prevent user mistakes by clearly delineating which options are applicable to each operation. Separating these options into operation-specific classes will improve clarity and ensure proper usage.

              Assignee:
              Slav Babanin
              Reporter:
              Slav Babanin
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: