You could implement some sort of sparse map. E.g. discard 9 out of 10
marks for anything more than 20 marks back. If they actually go back
that far again, you re-request from the nearest mark with a larger row
count.
And I would definitely add behavior analytic in this case. It may well
be that 14
Oh, I know I have problems! My (b) option of reversing sort and using the
current cursor mark is not working. It gets off by one record.
paging forward:
pg 1: docs 1-10
pg 2: docs 11-20
pg 3: docs 21-30
now paging backwards:
pg 2: docs 10-19
I'll go back to tracking all the cursor marks.
--
There was a similar discussion recently. I think the conclusion was that if
your users have to page through 5 millions of results, you have a bigger
problem on your hands than storing the page marks.
You could store them on the client side.
Regards,
Alex
On 02/02/2015 4:08 pm, "tedsolr"
