Nice.
this is the SQL i'm using, it works for MySQL but I'm not sure about
other databases, the "ORDER BY rc_id DESC LIMIT 1" should get you the
next oldest edit.
$sql = "SELECT rc_id, rc_cur_id, rc_moved_to_ns,
rc_moved_to_title, rc_new, rc_namespace, rc_title, rc_last_oldid
FROM recentchanges WHERE rc_id < $rcid and rc_patrolled = 0 ";
if ($show_namespace != null && $show_namespace != '')
// respect the filtered namespace
$sql .= " and rc_namespace " . ($invert ? '!=' : '=') .
$show_namespace ;
else
// avoid the delete logs, etc
$sql .= " and rc_namespace >= 0 ";
$sql .= " ORDER by rc_id DESC LIMIT 1";
Travis
On 6/21/06, Rob Church <robchur(a)gmail.com> wrote:
On 21/06/06, Travis Derouin <travis(a)wikihow.com>
wrote:
Hey,
I'm not sure if this has been suggested before, but on our wiki I
added in a feature that after someone is marks an edit as patrolled it
takes them to the next unpatrolled diff page. It keeps our community
members happy since they don't have to press the back button twice and
click on the next diff to get to the next unpatrolled edit. For 1.6 we
plan on passing along along any of the filter settings (namespace,
minor edit, etc) to choose the next diff.
I thought I'd share this in case anyone else is interested.
And what a coincidence; an extension to do this is in development!
Screenshot at
http://www.anubite.co.uk/mediawiki/SpecialPatrol.png.
It's more or less complete, although there is one problem for which I
need a good bit of SQL; right now, the query being run returns any old
unpatrolled change*, when it needs to return an unpatrolled change
which also happens to be the latest change to the respective page.
* Not exactly; any unpatrolled change not due to the patrolling user,
which wasn't bot marked and isn't "assigned" to another patroller.
Rob Church
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/wikitech-l
