From 769c739cde8ae4e8dc0e06140ab2196762e09a76 Mon Sep 17 00:00:00 2001 From: Chad Horohoe Date: Fri, 26 Jun 2009 22:09:34 +0000 Subject: [PATCH] Cleanup for r52382: Call correct function and use tmestamp() --- maintenance/updateSearchIndex.inc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/maintenance/updateSearchIndex.inc b/maintenance/updateSearchIndex.inc index 21e2df481b..032c35809b 100644 --- a/maintenance/updateSearchIndex.inc +++ b/maintenance/updateSearchIndex.inc @@ -20,8 +20,8 @@ function updateSearchIndex( $start, $end, $maxLockTime, $quiet ) { output( "Updating searchindex between $start and $end\n" ); # Select entries from recentchanges which are on top and between the specified times - $start = $dbw->strencode( $start ); - $end = $dbw->strencode( $end ); + $start = $dbw->strencode( $dbw->timestamp( $start ) ); + $end = $dbw->strencode( $dbw->timestamp( $end ) ); $page = $dbw->tableName( 'page' ); $sql = "SELECT rc_cur_id,rc_type,rc_moved_to_ns,rc_moved_to_title FROM $recentchanges @@ -90,7 +90,7 @@ function lockSearchindex( &$db ) { # Unlock and lock again # Since the lock is low-priority, queued reads will be able to complete function relockSearchindex( &$db ) { - unlockSearchindex( $db ); + lockSearchindex( $db ); $db->unlockTables( 'updateSearchIndex.inc ' . __METHOD__ ); } -- 2.20.1