CheckUserLog API: Support for query continue
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• bzimport
	Oct 1 2012, 11:21 AM

Description

Author: Amalthea.wikimedia

Description:
The ApiQueryCheckUserLog does not support query-continue logic. It would be nice if it did.

In fact, there's actually a bug in the module related to this: It already selects <tt>$limit + 1</tt> rows, presumably because it was based on a module that supported query-continue, so the result currently always contains one more row than requested.

Version: master
Severity: normal

Details

Reference: bz40658

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:52 AM

• bzimport added a project: CheckUser.

• bzimport set Reference to bz40658.

• bzimport created this task.Oct 1 2012, 11:21 AM

(In reply to comment #0)

In fact, there's actually a bug in the module related to this: It already
selects <tt>$limit + 1</tt> rows, presumably because it was based on a module
that supported query-continue, so the result currently always contains one more
row than requested.

$this->addOption( 'LIMIT', $limit + 1 );

Indeed. It also doesn't check if said results "fit" into the api resultset

Submitted patch in https://gerrit.wikimedia.org/r/#/c/33702/

Bug 43943 has been marked as a duplicate of this bug. ***

Merged by Yurik on the 8th.

Reedy set Security to None.Nov 29 2015, 2:02 PM

MarcoAurelio moved this task from Inbox to Done on the CheckUser board.May 9 2016, 8:57 AM

Restricted Application added a subscriber: JEumerus. · View Herald TranscriptMay 9 2016, 8:57 AM

Liuxinyu970226 removed a parent task: T25855: [ABANDONED TRACKING TASK] Non Core API issues.Mar 22 2019, 1:47 AM

CheckUserLog API: Support for query continueClosed, ResolvedPublicActions

Description

Details

Event Timeline

CheckUserLog API: Support for query continue
Closed, ResolvedPublic
Actions