Last modified: 2011-03-13 18:05:19 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 3936 - Recentchanges "... starting from ..." link does descending limit query instead of ascending
Recentchanges "... starting from ..." link does descending limit query instea...
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Lowest normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-11-12 08:07 UTC by Zigger
Modified: 2011-03-13 18:05 UTC (History)
1 user (show)

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


Description Zigger 2005-11-12 08:07:00 UTC
The Special:Recentchanges "... starting from ..." link returns a limited number
of rows (N) descending from the current time towards the "from" timestamp.  The
result on a busy wiki is that the newest N rows are shown instead of the oldest
N since the "from" timestamp, which is the same result as when no "from"
parameter is provided.

It looks to me as if the limit query should be ascending from the "from"
timestamp.  The stored results would then need to be reversed to display in
descending time order.
Comment 1 Aaron Schulz 2008-09-16 12:01:25 UTC
If anything, this is a wording issue. As long as it is clear that it means "changes newer than", it's fine. Also, this change would truncate the newest edits (which is odd) and break bots and such too.

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