[SERVER-5661] skip/limit has no effect when query with _id Created: 20/Apr/12 Updated: 05/Oct/15 Resolved: 05/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | kobevaliant | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
windows x64 |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
A query, for example, db.test.find({_id:"xxx"}).skip(1), will return a record, whatever the skip is. I didn't find something about this in doc, so I think this is a bug. |
| Comments |
| Comment by J Rassi [ 05/Oct/15 ] |
|
Closing as dup of |
| Comment by Eliot Horowitz (Inactive) [ 20/Apr/12 ] |
|
Interesting case, but definitely a bug. |