[SERVER-10627] Change in matching null against undefined in 2.5 vs 2.4 Created: 26/Aug/13  Updated: 27/Oct/15  Resolved: 02/Nov/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5.4

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-3130 null match now includes undefined Closed
Backwards Compatibility: Minor Change
Operating System: ALL
Participants:

 Description   

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



 Comments   
Comment by Eliot Horowitz (Inactive) [ 02/Nov/13 ]

Yes, intentional, need to double check docs are updated.

Generated at Thu Feb 08 03:23:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.