[DOCS-3180] Suggestion for /master/reference/operator/query/or/ Created: 15/Apr/14 Updated: 30/May/14 Resolved: 21/May/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.5 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Hannes Magnusson | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | audit-2014 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 39 weeks ago | ||||
| Description |
|
"New in version 1.6." This is a huge pythonism. 5(?)years later, this is still touted as a brand new feature.
How inefficient is nested $or (which is the second everybody-must-know about this feature - and you need to know it was added in 2.0).
Why not? How do I make it? Does it use any index? The example "document" is also weird.
Does it have to be the same index? Can the index be of different type? Why is $text so special? |
| Comments |
| Comment by Githook User [ 21/May/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |