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

[Tom Hughes]

I've changed it to sort by close time which should fix this for now but the whole thing seems a bit of a mess...

It would be better if everything used creation time because that would allow better optimisation when a user limit is included as we have an index on user+creation_time but not on user+close_time.

The time selection is also weird in that if you provide two bounds one is evaluated against close time and one against creation time?

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

Message ID: <openstreetmap/openstreetmap-website/pull/4164/c1676430257 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20230813/804d70ff/attachment.htm>