[DOCS-2454] document behavior change to $all: now interpreted as shorthand for $and Created: 23/Dec/13 Updated: 11/Jan/17 Resolved: 03/Jan/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | David Storch | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 10 years, 6 weeks, 6 days ago | ||||||||
| Description |
|
The new query system now interprets $all as syntactic sugar for $and. In some cases this can cause different query behavior in 2.5 compared to 2.4. See https://jira.mongodb.org/browse/SERVER-11785 for details. The 2.4.8 documentation (http://docs.mongodb.org/manual/reference/operator/query/all/) says the following: "The $all operator selects the documents where the value of a field is an array that contains all the specified elements." This is not strictly true now that $all is shorthand for $and. |
| Comments |
| Comment by Githook User [ 02/Jan/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |