[openstreetmap/openstreetmap-website] Filter out changesets that are too old when sorting in ascending order (PR #4164)

[Tom Hughes]

That makes the ordering stable but not the selection - as the selection was (primarily) on close time the set of selected changesets for a given time value could change between calls.

I think that can only happen if you use a selection time that is after the current time though, because any changeset that has a close time before the current time is closed and can't have it's close time move to later - if you use a selection time in the future then a changeset that had a close time before that can change to have a close time after it and hence get added to the selection for a future call.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/4164#issuecomment-1679763650
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/4164/c1679763650 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20230815/cda3cda0/attachment-0001.htm>