[DOCS-1860] Comment on: "manual/reference/operator/exists.txt" Created: 28/Aug/13 Updated: 03/Nov/17 Resolved: 25/Sep/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | auto | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 13.04, 64-bit. MongoDB version 2.4.3. Location: http://docs.mongodb.org/manual/reference/operator/exists/ |
||
| Participants: | |
| Days since reply: | 10 years, 21 weeks ago |
| Description |
|
In my installation of MongoDB 2.4.3, using $exists as part of an $elemMatch subquery returns elements with fields that exist but are null. This seems contrary to the behavior described in the documentation. Here's the excerpt from my MongoDB session: > db.rewards.findOne({ funds: { $elemMatch: { transactionHash: "915711f675abda802886039388f00feacbeaed843555fd173ca411d39bd30fa4", approved: {$exists: true}, }}}) ], |
| Comments |
| Comment by auto [ 25/Sep/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |