Last modified: 2011-03-13 18:05:30 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11789 - Paging for CheckUser results
Paging for CheckUser results
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-10-28 02:23 UTC by Dominic
Modified: 2011-03-13 18:05 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Dominic 2007-10-28 02:23:26 UTC
CU results, particularly for ranges or IPs with regular editors, can be very long. Right now it's not very flexible and can crash browsers when there is a large result. The results, both for "get edits" and "get users" should be paged like history or contributions pages, i.e. "View (previous 500) (next 500) (20 | 50 | 100 | 250 | 500)"
Comment 1 Aaron Schulz 2007-10-28 05:18:40 UTC
This could perhaps be done by storing a key with the user id, checked ip/name, and check type for a few hours. The key's existence would allow paging results without adding another log entry. I already have an index enhancement change held up due to the schema change, so I might as well see if I can fit this in.
Comment 2 Mike.lifeguard 2008-02-09 17:30:16 UTC
Could this potentially also incorporate the ability to go back to CU results without actually re-running the check, but instead just accessing a cached copy of the results accessible only to the CU who ran the check? (though, actually allowing any CU to see it would be nice, you can just say "look at these results" instead of copy-paste and emailing or what have you.
Comment 3 Aaron Schulz 2008-08-12 06:39:11 UTC
This is too inefficient, since it would keep retriggering the same large filesort per page view.

Note You need to log in before you can comment on or make changes to this bug.