[DOCS-4672] Comment on: "manual/reference/method/cursor.sort.txt" - conflicting statements Created: 15/Jan/15 Updated: 30/Oct/23 Resolved: 03/Apr/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Location: http://docs.mongodb.org/manual/reference/method/cursor.sort/ |
||
| Participants: | |
| Days since reply: | 8 years, 45 weeks, 5 days ago |
| Description |
|
Hi, Thanks for very concise and informative documentation on Mongodb. I found a conflicting statement on the use of combination of sort and limit with 'find' method. The page on sort says that we should limit the cursor size so that sorting is applied only on the limited set of data. But the page on find method states that find().sort().limit() will be treated in the same was as find().limit().sort() and limit() shall always be carried after find and sort operations. Which means that sorting cannot be carried out on limited set of found data. Can you please clear my doubt on this. I want to limit the data before applying sort on it as otherwise my application is crashing because of size of data in collection. Thanks, |
| Comments |
| Comment by Githook User [ 03/Apr/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 03/Apr/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: Conflicts: |