Inheritance diagram for ProtectedTitlesPager:

Collaboration diagram for ProtectedTitlesPager:

Public Member Functions
	__construct ($form, $conds=array(), $type, $level, $namespace, $sizetype='', $size=0)
	formatRow ($row)
	Abstract formatting function.
	getIndexField ()
	This function should be overridden to return the name of the index fi- eld.
	getQueryInfo ()
	getStartBody ()
	Hook into getBody(), allows text to be inserted at the start.
	getTitle ()
Public Attributes
	$mConds
	$mForm

Detailed Description

Todo:: document

Definition at line 191 of file SpecialProtectedtitles.php.

Constructor & Destructor Documentation

ProtectedTitlesPager::__construct	(	$	form,
		$	conds = `array()`,
		$	type,
		$	level,
		$	namespace,
		$	sizetype = `''`,
		$	size = `0`
	)

Definition at line 194 of file SpecialProtectedtitles.php.

References $size.

Member Function Documentation

ProtectedTitlesPager::formatRow ( $ row )

Abstract formatting function.

This should return an HTML string representing the result row $row. Rows will be concatenated and returned by getBody()

Parameters:

$row	Object: database row

Returns:: String

Reimplemented from IndexPager.

Definition at line 225 of file SpecialProtectedtitles.php.

ProtectedTitlesPager::getIndexField ( )

This function should be overridden to return the name of the index fi- eld.

If the pager supports multiple orders, it may return an array of 'querykey' => 'indexfield' pairs, so that a request with &count=querykey will use indexfield to sort. In this case, the first returned key is the default.

Needless to say, it's really not a good idea to use a non-unique index for this! That won't page right.