This was suggested in
https://github.com/openstreetmap/openstreetmap-website/pull/4571#issuecomment-1994856482
but I haven't done it because we don't have appropriate indexes. This requires
reading all changeset node/ways/relations and sorting them. We also have counts
of changeset elements but at least counting doesn't require sorting.
Also if you want the pagination here to be closer to like it is for traces,
diary entries etc
(https://github.com/openstreetmap/openstreetmap-website/pull/5205#issuecomment-2346879691),
that's done with sorting by some id. We can't sort changeset elements just by
id because ids are not unique, you can have several versions of the same
element. That's why this PR sorts by (id, version) but it's not quite the same
as in other places. What would have made it nearly the same is something like
#4660.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5209#issuecomment-2352910968
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/5209/c2352910...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
