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

update considers a change in numerical type to be a noop

XMLWordPrintableJSON

    • Minor Change
    • ALL
    • Hide 
      db.foo.insert({f1:0})
db.foo.update({},{$set:{f1:NumberInt(0)}})
WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 0 })
      Show
      db.foo.insert({f1:0}) db.foo.update({},{$set:{f1:NumberInt(0)}}) WriteResult({ "nMatched" : 1, "nUpserted" : 0, "nModified" : 0 })
    • QuInt E (01/11/16), Query F (02/01/16), Query 10 (02/22/16), Query 11 (03/14/16)
    • 0
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      When trying to set value of one numerical type to the same number of different numerical type, the update treats it as a noop and doesn't update the field.

            Assignee:
            david.storch@mongodb.com David Storch
            Reporter:
            asya.kamsky@mongodb.com Asya Kamsky
            Votes:
            5 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated:
              Resolved: