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

Minor issues with new delete write command

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 2.5.4
    • Affects Version/s: 2.5.4
    • Component/s: Write Ops
    • None
    • ALL

      First issue: if you omit the "limit" field from a delete request, the error message returned erroneously says that "ordered" is mising:

      > db.runCommand({
      ... delete:"testcollection",
      ... writeConcern : { w : 1 },
      ... deletes : [{ q : { x : 1 } }, { q : { x : 3 } }]
      ... })
      { "ok" : false, "errCode" : 99999, "errMsg" : "missing ordered field" }
      > db.test.remove
      

      Second issue: the server should accept any numeric type for the limit value. When I sent an Int64 limit I got this error message:

      "{ 'ok' : false, 'errCode' : 99999, 'errMsg' : 'wrong type for 'limit' field, expected integer, found limit: 1' }"
      

            Assignee:
            greg_10gen Greg Studer
            Reporter:
            robert@mongodb.com Robert Stam
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: