[openstreetmap/openstreetmap-website] /user/<username>/history needs browser history memory (#1089)

Tom Hughes notifications at github.com
Fri Apr 15 13:08:38 UTC 2016


That value on the user page is actually a special cache, not the real count.

Numbered pagination needs to go pretty much everywhere, precisely because it requires all the records to be counted to determine how many pages there are and then when page N is visited you have to read through all the records in order to find the right ones. That's why it gets noticeably slower the further down the list you go, and it's far worse when a search engine decides to visit all the pages...

The correct solution is to do pagination based on an indexed field (either the changeset ID or the timestamp in this case) so that viewing the hundredth page can be done by an indexed lookup. That is in fact exactly how this particular already works I believe, it just doesn't put that marker value in the URL at the moment.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1089#issuecomment-210459018
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20160415/4e51d2a9/attachment.html>


More information about the rails-dev mailing list