Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8552

setParameter command has confusing behavior when setting multiple parameters.

    XMLWordPrintable

    Details

    • Operating System:
      ALL

      Description

      The result of a successful setParameter with one parameter to set is

      { was: <old value>, ok: 1 }

      . However, if you set two parameters, you get back

      { was: <first old value>, was: <second old value>, ok: 1}

      , which many client drivers seem to turn into

      { was: <one of the old values>, ok: 1}

      .

      Further, if you pass multiple parameters to setParameter, and one of the sets fails, some of the parameters will have been set and some not, and the response will contain a "was" field for one of the successful sets, ok: 0 and errmsg of "not allowed to change [<first encountered unsettable field>]" or some such.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-platform DO NOT USE - Backlog - Platform Team
              Reporter:
              schwerin Andy Schwerin
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: