[DOCS-8370] 3.2 compatibility page should mention stricter validation for skip & limit Created: 17/Jul/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | mongodb-3.2 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Stennie Steneker (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
MongoDB 3.2 implemented find as a command (SERVER-15176), which includes improvements for the type validation of options such as skip and limit. The legacy query protocol allows skip & limit to be provided as strings. Clients/drivers updated to use the new 3.2 protocol must provide skip and limit values as integers as documented on: https://docs.mongodb.com/manual/reference/command/find/#dbcmd.find. This should be mentioned on the 3.2 compatibility page: https://docs.mongodb.com/manual/release-notes/3.2-compatibility/. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |