[SERVER-1168] Allow skip on existing cursor Created: 27/May/10 Updated: 04/Jul/10 Resolved: 27/May/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 1.5.3 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Allow existing cursor to respond to skip requests from client. It seems this could be done by adding an offset (skip) to OP_GETMORE when requesting the next batch, or by adding a new OP_UPDATECURSOR to set the position in the cursor (thus allowing movement in both directions), or even changing the fields to be returned. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 27/May/10 ] |
|
I don't think this really makes sense. |