Throw a DBException wherever “code” was appended previously

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability
    • Fully Compatible
    • Service arch 2020-07-13, Service Arch 2020-08-10, Service Arch 2020-08-24, Service arch 2020-09-07, Service arch 2020-09-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Wherever we would append a code field that was not part of a WriteResult subobject, we should instead throw a DBException. In some cases, this may involve encoding additional information into our DBException, but the conversion itself should not be complicated. There may be problems with existing try-catch blocks that encoded into the BSONObj. The solution is to structure a makeGuard() to achieve the catch behavior.

              Assignee:
              Unassigned
              Reporter:
              Benjamin Caimano (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: