[DOCS-8091] Comment on: "primer/query.txt" Created: 13/Jun/16 Updated: 03/Nov/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/getting-started/node/query/ |
||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Description |
|
Please be aware that this page on querying a mongodb database is part of a linked series of tutorial pages that early on inserts data into the restaurants collection from the primer-dataset.json sample data set file. So on the page where queries is introduced, although the previous page on inserting data inserted a single document, the restaurants collection is populated with a very large set of data. The result is that when executing the query using find() with no filters, the query outputs a very large number of records. For the beginning student of mongodb, because the previous page inserted a single document, the problem may not be obvious. |
| Comments |
| Comment by Kay Kim (Inactive) [ 27/Jul/16 ] |
|
Jira housekeeping as we are undergoing projects for driver documentation. If you require additional support, please open a new ticket for prioritization. Regards, Kay Kim |