[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:
Related
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.

  • The version number should be link to the release notes
  • Was it 1.6 or 2.6 that was just released? Or 3.6? Can I safely use this feature?
    • Takes up way to much precious screen real-estate for no gain
    • We don't maintain multiple major branches so why do I care it was added before current stable major release?
  • Why are the documents both versioned and changes kept inline? pick one.

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).

This modified query will not use the index on price nor the index on sale.

Why not? How do I make it? Does it use any index?

The example "document" is also weird.
The inventory contains a mix of items and already sold items?
Is it really good practice to create an index on a boolean field?
Is 'quantity' to long fieldname so we have to use 'qty'?

If $or includes a $text query, all clauses in the $or array must be indexed.

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: DOCS-3180 update or operator page
Branch: master
https://github.com/mongodb/docs/commit/6e29306a690d002c5497c49658c1ad61281a2f28

Generated at Thu Feb 08 07:45:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.