Change in matching null against undefined in 2.5 vs 2.4

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Minor Change
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Not sure if this is intentional or not.

      Setup:

      > db.z.drop()
      true
      > db.z.insert({})
      > db.z.insert({a:null})
      > db.z.insert({a:undefined})
      

      2.4:

      > db.z.find({a:null})
      { "_id" : ObjectId("521bc5133f824429a66880d6") }
      { "_id" : ObjectId("521bc5153f824429a66880d7"), "a" : null }
      

      2.5:

      > db.z.find({a:null})
      { "_id" : ObjectId("521bc5133f824429a66880d6") }
      { "_id" : ObjectId("521bc5153f824429a66880d7"), "a" : null }
      { "_id" : ObjectId("521bc5183f824429a66880d8"), "a" : null } // really undefined
      

            Assignee:
            Eliot Horowitz (Inactive)
            Reporter:
            Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: