Feature proposal #6755
closed
Redo paging without pagenav
Added by krileon over 6 years ago.
Updated over 6 years ago.
Start date:
01 September 2017
Description
Redo the paging code to not use pagenav. The stream should define the limit and what page it's on. The next page should always be current page + limit and be set after every call. If rows are removed and it's looped then it'll be able to take the loop count into account. PageNav class isn't providing anything here in this case.
Implement support for linking to a page. This basically already works, but it's rather complicated as it has to include a unique stream name. See if there's a way of doing this more easily to allow for linking to stream pages.
This should take into consideration the auto update usage. If the next page starts at 28 and 3 entries were added it should increment the next page by 3 to account for the new entries pushing the activity available down. Maybe a better paging option would just be timestamp based?
- Target version changed from 6.0.0 to 4.1.0
Just do this using timestamp based paging. This completely eliminates issues with needing to calculate when the next page is.
- Target version changed from 4.1.0 to 6.0.0
- Target version changed from 6.0.0 to 4.2.0
- Status changed from Assigned to Rejected
- Target version deleted (
4.2.0)
- % Done changed from 0 to 100
Not possible. Timestamp based will cause entries with same timestamp to be lost. For example I want 15 entries. It stops at 15 entries. The 16th entry has the same timestamp as the 15th entry. That entry is then lost since we're only grabbing entries greater than the specified timestamp.
Also available in: Atom
PDF
Updated by