Last modified: 2007-01-03 16:29:37 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 8200 - Special:Categories is unsorted in PostgreSQL
Special:Categories is unsorted in PostgreSQL
Product: MediaWiki
Classification: Unclassified
Categories (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: postgres
  Show dependency treegraph
Reported: 2006-12-09 15:15 UTC by Sven Klemm
Modified: 2007-01-03 16:29 UTC (History)
0 users

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

patch to sort the entries in Special:Categories (624 bytes, patch)
2006-12-09 15:17 UTC, Sven Klemm

Description Sven Klemm 2006-12-09 15:15:59 UTC
Currently the Special:Categories lists the categories completely unsorted. It
would be nice if the categories were sorted.
Comment 1 Sven Klemm 2006-12-09 15:17:55 UTC
Created attachment 2847 [details]
patch to sort the entries in Special:Categories
Comment 2 Greg Sabino Mullane 2006-12-09 15:51:14 UTC
Thanks, fixed in r18240. Also patched SpecialUnusedCategories.php

Apparently, mysql does an implicit sort, so this was working until Postgres was
Comment 3 JeLuF 2006-12-31 13:36:28 UTC
closing, since no reason was given for the re-opening.
Comment 4 Sven Klemm 2006-12-31 13:45:48 UTC
Reopening because the patch has been reverted in r18458.
Comment 5 Greg Sabino Mullane 2007-01-02 21:35:32 UTC
Attempted a different approach with r18771.

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