[DOCS-21] The description for $in does not mention that it can be used with arrays nor does it explain the behavior when it is Created: 03/Jan/11 Updated: 04/Nov/13 Resolved: 08/Mar/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Mercer | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 15 weeks, 3 days ago |
| Description |
|
The documentation states that "The $in operator is analogous to the SQL IN modifier, allowing you to specify an array of possible matches." But it appears to also work when applied to an array in the database. The documentation should define exactly what $in means when both argument and database are arrays. The behavior appears to be any element in the database array field is $in the query array. |
| Comments |
| Comment by auto [ 04/Nov/13 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Sam Kleinman (Inactive) [ 08/Mar/12 ] |
|
I'm very sorry about the delay in following up with this issue. Fixed in the new documentation (i.e. the Manual) that should be published sometime in the next week. |
| Comment by auto [ 08/Mar/12 ] |
|
Author: {u'login': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |