<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>That would not really solve Martins problem, for example if you
want to find a changeset that in the middle of the "7000".</p>
<p>The reasonably lightweight solution is to have a (collapsible)
date selector for selecting either changeset before the data or
after (changing the sorting), which wouldn't require changing the
basic way things work.</p>
<p>@Martin the paging has been gone for roughly 3 years or so, it is
a bit late complaining now.</p>
<p>Simon<br>
</p>
<br>
<div class="moz-cite-prefix">Am 13.10.2016 um 11:26 schrieb Colin
Smale:<br>
</div>
<blockquote cite="mid:6fc3b0378c0433a9271e14847fe4e6f8@xs4all.nl"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>how about having the option of sorting the list by ascending
date, so the oldest come first? </p>
<div> </div>
<p> </p>
<p>On 2016-10-13 11:22, Tom Hughes wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<p>Unfortunately they don't "work" for the poor server that in
order to find page 7000 has to search through the preceding
6999*pagesize changesets.</p>
<p>Basically traditional paging is not sustainable on large
datasets because each page is slower and slower to access as
it has to read through the data for all the previous pages
first and the simple fact is that no real person is actually
going to browse through 7000 pages!</p>
<p>Presumably what you are really doing is binary searching by
manually editing the URL to find the page which covers a
particular date range you are interested in. Which puts you in
the 0.001% of users that would have any idea how to do that.</p>
<p>The real solution, if I am right about what you are doing, is
to add better methods to search for changesets by a given user
in a given date range (which the server can do efficiently)
not to bring back paging.</p>
<p style="font-size: small; -webkit-text-size-adjust: none;
color: #666;">—<br>
You are receiving this because you are subscribed to this
thread.<br>
Reply to this email directly, <a moz-do-not-send="true"
href="https://github.com/openstreetmap/openstreetmap-website/issues/1323#issuecomment-253461175">view
it on GitHub</a>, or <a moz-do-not-send="true"
href="https://github.com/notifications/unsubscribe-auth/ABWnLToDuFdtV64bL0jcTELbpfT2u69pks5qzfhRgaJpZM4KVmZB">mute
the thread</a>.<img moz-do-not-send="true"
src="program/resources/blocked.gif" alt="" height="1"
width="1"></p>
<div>
<div><!-- link ignored --><!-- meta ignored --></div>
<!-- meta ignored --></div>
<!-- script not allowed --><br>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace">_______________________________________________<br>
rails-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:rails-dev@openstreetmap.org">rails-dev@openstreetmap.org</a><br>
<a moz-do-not-send="true"
href="https://lists.openstreetmap.org/listinfo/rails-dev">https://lists.openstreetmap.org/listinfo/rails-dev</a></div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rails-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rails-dev@openstreetmap.org">rails-dev@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/rails-dev">https://lists.openstreetmap.org/listinfo/rails-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>