[DOCS-3449] Doc that $where must be top-level Created: 21/May/14 Updated: 16/Mar/15 Resolved: 18/Jun/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 9 years, 35 weeks ago | ||||||||||||||||
| Description |
|
2.6 strictly enforces that a $where query operator must be a field of the top-level document. It cannot be inside a nested document (for instance, below an $elemMatch). Can we add this as a note here: http://docs.mongodb.org/manual/reference/operator/query/where/? 2.4 erroneously allowed $where inside an $elemMatch value, so it might be worth tagging this as "changed in 2.6". See relevant core server tickets for details: |
| Comments |
| Comment by Githook User [ 18/Jun/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| Comment by Sam Kleinman (Inactive) [ 21/May/14 ] |
|
should also add something to the compatibility note section. |