I was just checking out who earned the most of the new badges that were announced this week. I have a SEDE query for this which sorts by default on the number of sites you earned a badge. I noticed that when I run it for the harder badge, Lifeboat (awarded to 1089 users on the network), I can click on the column headers to change the sorting:

enter image description here

However, for Lifejacket, awarded to 10104 users (which is less than SEDE's maximum of 50000), sorting the results doesn't work:

enter image description here

(I am aware that I can just change the ORDER BY in the final SELECT statement, but then I need to maintain two queries. Also, I can make the sorting depend on another parameter, but I'm too lazy ...)

@rene points out in the comments that it's a deliberate choice and blindly increasing this number may still lead to performance problems with 2019's browsers. Therefore, it's now a formal to redesign the grid (or implement another library) so that sorting is always possible.

  • 2
    Sort is disabled for resultsets with more then 5000 rows. This is a limitation of the used grid control. – rene Jun 23 at 11:33
  • related: meta.stackexchange.com/a/307608/158100 – rene Jun 23 at 11:34
  • And I guess that there's no simple way to crank that up to 50,000, since somebody would've already done that? – Glorfindel Jun 23 at 11:35
  • 3
    Here is the original implementation answer: meta.stackexchange.com/questions/51966/… – rene Jun 23 at 11:36
  • We could crank it up but we might crank down every reasonable browser who views a resultset. Your call .... – rene Jun 23 at 11:37
  • 1
    Internet Explorer (at least the version that existed back in 2013) does not fall under my definition of 'reasonable browser'. – Glorfindel Jun 23 at 11:38
  • 1
    well, let me run an experiment in the next 6 to 8 days to see if this limitation is no longer an issue. But that has to wait a bit as I'm not near a dev-box that has a local running SEDE. – rene Jun 23 at 11:39
  • Okay, the setting is hardcoded here and I have done an experiment with 32000 rows. There is a considerable lag / hang when the 32000 rows are added to the DOM. Think in the order of 5 to 10 seconds in IE11. After that sorting is smooth and quick. Just the initial load is suboptimal. – rene Jun 23 at 19:05
  • At this moment I think ramping up that value to 50000 is not a good call. This needs an overhaul of that grid to address this and a couple of other issues. – rene Jun 23 at 19:08

You must log in to answer this question.

Browse other questions tagged .