https://bugzilla.wikimedia.org/show_bug.cgi?id=12363
--- Comment #22 from Steven Walling <[email protected]> --- (In reply to comment #21) > > The above solution is only good for enwiki though. If it's inordinately > > difficult to add recent moves to Special:NewPages, then I think Option 2, > > and > > creation of a proper Special:RecentMoves, would be the ideal case for most > > Wikimedia wikis. > > > > Ideally, a Special:RecentMoves would... > > > > * Be able to be filtered by moves within any namespace > > * Be able to be filtered down to cross-namespace moves > > > > Brian, I added Dan Garry to this bug, as it seems like it's a part of > > Platform's remit. Dan, does that sound reasonable? > > Hmm, I wonder what the performance implications of Select * from > recentchanges > inner join page on page_id = rc_cur_id where rc_new = 1 and rc_namespace != > page_namespace and page_namespace = 0; Seems like that would be a bit more > scary then what normally can go on 'pedia. Then again, that's probably > similar > to the performance of Special:Recentchangeslinked, so maybe... [Saying this > without doing any testing whatsoever, probably totally wrong]. Stupid question: since this filtering is done by the user, is it perhaps better to gather the list of all moves, then do a filter for moves where the new/target namespace is mismatched on the client side, rather than in SQL? Since nothing would prevent users without JS from viewing the list, that seems like a nice to have feature. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
