https://bugzilla.wikimedia.org/show_bug.cgi?id=55377
Web browser: ---
Bug ID: 55377
Summary: API: Implement rctitles parameter in
query=recentchanges
Product: MediaWiki
Version: 1.22-git
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: Unprioritized
Component: API
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected]
Classification: Unclassified
Mobile Platform: ---
See also:
* bug 12394 (make it easier to retrieve rcid of a newpage creation)
* bug 15552 (things like Special:RecentChangesLinked and in order to use a
generator module with recentchanges)
This would enable:
* Getting rcid of an unpatrolled page creation from the API.
* Use recentchanges with a generator module.
* Use recentchanges with watch list (maybe?).
* Allow tools to mass-patrol all unpatrolled changes to a single page.
(bug 12394 comment #7)
> (bug 12394 comment #6)
> > (bug 12394 comment #5)
> > > However, I see in the current database structure there's a seperate
> > > column for
> > > rc_title.
> > > I'm not sure since when this exists, and/or if it was originally
> > > utilized, but
> > > when using that in the query (AND WHERE rc_title='Foobar') it'd be like
> > > any
> > > other condition currently in the recentchanges API right (same thing for
> > > rc_user, with $this->addWhereFld(); )
> > >
> > The original implementation did do a WHERE on rc_namespace and rc_title,
> > yes,
> > but that's not the same as doing a WHERE on rc_user because the latter is
> > indexed. Implementing this feature would require adding an index for it
> > (kinda
> > leery of that) and even then it'd have to sort by namespace, then title,
> > then
> > timestamp in order to work efficiently.
>
> There is a rc_namespace_title index though. But unlike the one for rc_user,
> it
> doesn't have rc_timestamp.
>
> mediawiki-core@master:/maintenance/tables.sql:
> INDEX rc_timestamp ON recentchanges (rc_timestamp);
> INDEX rc_namespace_title ON recentchanges (rc_namespace, rc_title);
> INDEX rc_cur_id ON recentchanges (rc_cur_id);
> INDEX new_name_timestamp ON recentchanges
> (rc_new,rc_namespace,rc_timestamp);
> INDEX rc_ip ON recentchanges (rc_ip);
> INDEX rc_ns_usertext ON recentchanges (rc_namespace, rc_user_text);
> INDEX rc_user_text ON recentchanges (rc_user_text, rc_timestamp);
>
>
> Would it make sense for rc_namespace_title to have it? I wonder what it is
> used
> for and if those uses would have a problem with the extra rc_timestamp sort.
> The default sort for rc_namespace_title is presumably rc_id which should have
> be very close to the sort order of rc_timestamp.
>
> The main reason it needs rc_timestamp is not for the sort order, but to be
> able
> to do rcstart and rcend.
--
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
