MediaWiki  REL1_31
updateCollation.php
Go to the documentation of this file.
1 <?php
27 require_once __DIR__ . '/Maintenance.php';
28 
30 
38  const BATCH_SIZE = 100; // Number of rows to process in one batch
39  const SYNC_INTERVAL = 5; // Wait for replica DBs after this many batches
40 
41  public $sizeHistogram = [];
42 
43  public function __construct() {
44  parent::__construct();
45 
47  $this->addDescription( <<<TEXT
48 This script will find all rows in the categorylinks table whose collation is
49 out-of-date (cl_collation != '$wgCategoryCollation') and repopulate cl_sortkey
50 using the page title and cl_sortkey_prefix. If all collations are
51 up-to-date, it will do nothing.
52 TEXT
53  );
54 
55  $this->addOption( 'force', 'Run on all rows, even if the collation is ' .
56  'supposed to be up-to-date.', false, false, 'f' );
57  $this->addOption( 'previous-collation', 'Set the previous value of ' .
58  '$wgCategoryCollation here to speed up this script, especially if your ' .
59  'categorylinks table is large. This will only update rows with that ' .
60  'collation, though, so it may miss out-of-date rows with a different, ' .
61  'even older collation.', false, true );
62  $this->addOption( 'target-collation', 'Set this to the new collation type to ' .
63  'use instead of $wgCategoryCollation. Usually you should not use this, ' .
64  'you should just update $wgCategoryCollation in LocalSettings.php.',
65  false, true );
66  $this->addOption( 'dry-run', 'Don\'t actually change the collations, just ' .
67  'compile statistics.' );
68  $this->addOption( 'verbose-stats', 'Show more statistics.' );
69  }
70 
71  public function execute() {
73 
74  $dbw = $this->getDB( DB_MASTER );
75  $dbr = $this->getDB( DB_REPLICA );
76  $force = $this->getOption( 'force' );
77  $dryRun = $this->getOption( 'dry-run' );
78  $verboseStats = $this->getOption( 'verbose-stats' );
79  if ( $this->hasOption( 'target-collation' ) ) {
80  $collationName = $this->getOption( 'target-collation' );
81  $collation = Collation::factory( $collationName );
82  } else {
83  $collationName = $wgCategoryCollation;
84  $collation = Collation::singleton();
85  }
86 
87  // Collation sanity check: in some cases the constructor will work,
88  // but this will raise an exception, breaking all category pages
89  $collation->getFirstLetter( 'MediaWiki' );
90 
91  // Locally at least, (my local is a rather old version of mysql)
92  // mysql seems to filesort if there is both an equality
93  // (but not for an inequality) condition on cl_collation in the
94  // WHERE and it is also the first item in the ORDER BY.
95  if ( $this->hasOption( 'previous-collation' ) ) {
96  $orderBy = 'cl_to, cl_type, cl_from';
97  } else {
98  $orderBy = 'cl_collation, cl_to, cl_type, cl_from';
99  }
100  $options = [
101  'LIMIT' => self::BATCH_SIZE,
102  'ORDER BY' => $orderBy,
103  'STRAIGHT_JOIN' // per T58041
104  ];
105 
106  if ( $force ) {
107  $collationConds = [];
108  } else {
109  if ( $this->hasOption( 'previous-collation' ) ) {
110  $collationConds['cl_collation'] = $this->getOption( 'previous-collation' );
111  } else {
112  $collationConds = [ 0 =>
113  'cl_collation != ' . $dbw->addQuotes( $collationName )
114  ];
115  }
116 
117  $count = $dbr->estimateRowCount(
118  'categorylinks',
119  '*',
120  $collationConds,
121  __METHOD__
122  );
123  // Improve estimate if feasible
124  if ( $count < 1000000 ) {
125  $count = $dbr->selectField(
126  'categorylinks',
127  'COUNT(*)',
128  $collationConds,
129  __METHOD__
130  );
131  }
132  if ( $count == 0 ) {
133  $this->output( "Collations up-to-date.\n" );
134 
135  return;
136  }
137  if ( $dryRun ) {
138  $this->output( "$count rows would be updated.\n" );
139  } else {
140  $this->output( "Fixing collation for $count rows.\n" );
141  }
142  wfWaitForSlaves();
143  }
144  $count = 0;
145  $batchCount = 0;
146  $batchConds = [];
147  do {
148  $this->output( "Selecting next " . self::BATCH_SIZE . " rows..." );
149 
150  // cl_type must be selected as a number for proper paging because
151  // enums suck.
152  if ( $dbw->getType() === 'mysql' ) {
153  $clType = 'cl_type+0 AS "cl_type_numeric"';
154  } else {
155  $clType = 'cl_type';
156  }
157  $res = $dbw->select(
158  [ 'categorylinks', 'page' ],
159  [ 'cl_from', 'cl_to', 'cl_sortkey_prefix', 'cl_collation',
160  'cl_sortkey', $clType,
161  'page_namespace', 'page_title'
162  ],
163  array_merge( $collationConds, $batchConds, [ 'cl_from = page_id' ] ),
164  __METHOD__,
165  $options
166  );
167  $this->output( " processing..." );
168 
169  if ( !$dryRun ) {
170  $this->beginTransaction( $dbw, __METHOD__ );
171  }
172  foreach ( $res as $row ) {
173  $title = Title::newFromRow( $row );
174  if ( !$row->cl_collation ) {
175  # This is an old-style row, so the sortkey needs to be
176  # converted.
177  if ( $row->cl_sortkey == $title->getText()
178  || $row->cl_sortkey == $title->getPrefixedText()
179  ) {
180  $prefix = '';
181  } else {
182  # Custom sortkey, use it as a prefix
183  $prefix = $row->cl_sortkey;
184  }
185  } else {
186  $prefix = $row->cl_sortkey_prefix;
187  }
188  # cl_type will be wrong for lots of pages if cl_collation is 0,
189  # so let's update it while we're here.
190  if ( $title->getNamespace() == NS_CATEGORY ) {
191  $type = 'subcat';
192  } elseif ( $title->getNamespace() == NS_FILE ) {
193  $type = 'file';
194  } else {
195  $type = 'page';
196  }
197  $newSortKey = $collation->getSortKey(
198  $title->getCategorySortkey( $prefix ) );
199  if ( $verboseStats ) {
200  $this->updateSortKeySizeHistogram( $newSortKey );
201  }
202 
203  if ( $dryRun ) {
204  // Add 1 to the count if the sortkey was changed. (Note that this doesn't count changes in
205  // other fields, if any, those usually only happen when upgrading old MediaWikis.)
206  $count += ( $row->cl_sortkey !== $newSortKey );
207  } else {
208  $dbw->update(
209  'categorylinks',
210  [
211  'cl_sortkey' => $newSortKey,
212  'cl_sortkey_prefix' => $prefix,
213  'cl_collation' => $collationName,
214  'cl_type' => $type,
215  'cl_timestamp = cl_timestamp',
216  ],
217  [ 'cl_from' => $row->cl_from, 'cl_to' => $row->cl_to ],
218  __METHOD__
219  );
220  $count++;
221  }
222  if ( $row ) {
223  $batchConds = [ $this->getBatchCondition( $row, $dbw ) ];
224  }
225  }
226  if ( !$dryRun ) {
227  $this->commitTransaction( $dbw, __METHOD__ );
228  }
229 
230  if ( $dryRun ) {
231  $this->output( "$count rows would be updated so far.\n" );
232  } else {
233  $this->output( "$count done.\n" );
234  }
235  } while ( $res->numRows() == self::BATCH_SIZE );
236 
237  if ( !$dryRun ) {
238  $this->output( "$count rows processed\n" );
239  }
240 
241  if ( $verboseStats ) {
242  $this->output( "\n" );
243  $this->showSortKeySizeHistogram();
244  }
245  }
246 
254  function getBatchCondition( $row, $dbw ) {
255  if ( $this->hasOption( 'previous-collation' ) ) {
256  $fields = [ 'cl_to', 'cl_type', 'cl_from' ];
257  } else {
258  $fields = [ 'cl_collation', 'cl_to', 'cl_type', 'cl_from' ];
259  }
260  $first = true;
261  $cond = false;
262  $prefix = false;
263  foreach ( $fields as $field ) {
264  if ( $dbw->getType() === 'mysql' && $field === 'cl_type' ) {
265  // Range conditions with enums are weird in mysql
266  // This must be a numeric literal, or it won't work.
267  $encValue = intval( $row->cl_type_numeric );
268  } else {
269  $encValue = $dbw->addQuotes( $row->$field );
270  }
271  $inequality = "$field > $encValue";
272  $equality = "$field = $encValue";
273  if ( $first ) {
274  $cond = $inequality;
275  $prefix = $equality;
276  $first = false;
277  } else {
278  $cond .= " OR ($prefix AND $inequality)";
279  $prefix .= " AND $equality";
280  }
281  }
282 
283  return $cond;
284  }
285 
286  function updateSortKeySizeHistogram( $key ) {
287  $length = strlen( $key );
288  if ( !isset( $this->sizeHistogram[$length] ) ) {
289  $this->sizeHistogram[$length] = 0;
290  }
291  $this->sizeHistogram[$length]++;
292  }
293 
295  $maxLength = max( array_keys( $this->sizeHistogram ) );
296  if ( $maxLength == 0 ) {
297  return;
298  }
299  $numBins = 20;
300  $coarseHistogram = array_fill( 0, $numBins, 0 );
301  $coarseBoundaries = [];
302  $boundary = 0;
303  for ( $i = 0; $i < $numBins - 1; $i++ ) {
304  $boundary += $maxLength / $numBins;
305  $coarseBoundaries[$i] = round( $boundary );
306  }
307  $coarseBoundaries[$numBins - 1] = $maxLength + 1;
308  $raw = '';
309  for ( $i = 0; $i <= $maxLength; $i++ ) {
310  if ( $raw !== '' ) {
311  $raw .= ', ';
312  }
313  if ( !isset( $this->sizeHistogram[$i] ) ) {
314  $val = 0;
315  } else {
316  $val = $this->sizeHistogram[$i];
317  }
318  for ( $coarseIndex = 0; $coarseIndex < $numBins - 1; $coarseIndex++ ) {
319  if ( $coarseBoundaries[$coarseIndex] > $i ) {
320  $coarseHistogram[$coarseIndex] += $val;
321  break;
322  }
323  }
324  if ( $coarseIndex == $numBins - 1 ) {
325  $coarseHistogram[$coarseIndex] += $val;
326  }
327  $raw .= $val;
328  }
329 
330  $this->output( "Sort key size histogram\nRaw data: $raw\n\n" );
331 
332  $maxBinVal = max( $coarseHistogram );
333  $scale = 60 / $maxBinVal;
334  $prevBoundary = 0;
335  for ( $coarseIndex = 0; $coarseIndex < $numBins; $coarseIndex++ ) {
336  if ( !isset( $coarseHistogram[$coarseIndex] ) ) {
337  $val = 0;
338  } else {
339  $val = $coarseHistogram[$coarseIndex];
340  }
341  $boundary = $coarseBoundaries[$coarseIndex];
342  $this->output( sprintf( "%-10s %-10d |%s\n",
343  $prevBoundary . '-' . ( $boundary - 1 ) . ': ',
344  $val,
345  str_repeat( '*', $scale * $val ) ) );
346  $prevBoundary = $boundary;
347  }
348  }
349 }
350 
352 require_once RUN_MAINTENANCE_IF_MAIN;
UpdateCollation\SYNC_INTERVAL
const SYNC_INTERVAL
Definition: updateCollation.php:39
use
Apache License January AND DISTRIBUTION Definitions License shall mean the terms and conditions for use
Definition: APACHE-LICENSE-2.0.txt:10
is
We use the convention $dbr for read and $dbw for write to help you keep track of whether the database object is a the world will explode Or to be a subsequent write query which succeeded on the master may fail when replicated to the slave due to a unique key collision Replication on the slave will stop and it may take hours to repair the database and get it back online Setting read_only in my cnf on the slave will avoid this but given the dire we prefer to have as many checks as possible We provide a but the wrapper functions like please read the documentation for except in special pages derived from QueryPage It s a common pitfall for new developers to submit code containing SQL queries which examine huge numbers of rows Remember that COUNT * is(N), counting rows in atable is like counting beans in a bucket.------------------------------------------------------------------------ Replication------------------------------------------------------------------------The largest installation of MediaWiki, Wikimedia, uses a large set ofslave MySQL servers replicating writes made to a master MySQL server. Itis important to understand the issues associated with this setup if youwant to write code destined for Wikipedia.It 's often the case that the best algorithm to use for a given taskdepends on whether or not replication is in use. Due to our unabashedWikipedia-centrism, we often just use the replication-friendly version, but if you like, you can use wfGetLB() ->getServerCount() > 1 tocheck to see if replication is in use.===Lag===Lag primarily occurs when large write queries are sent to the master.Writes on the master are executed in parallel, but they are executed inserial when they are replicated to the slaves. The master writes thequery to the binlog when the transaction is committed. The slaves pollthe binlog and start executing the query as soon as it appears. They canservice reads while they are performing a write query, but will not readanything more from the binlog and thus will perform no more writes. Thismeans that if the write query runs for a long time, the slaves will lagbehind the master for the time it takes for the write query to complete.Lag can be exacerbated by high read load. MediaWiki 's load balancer willstop sending reads to a slave when it is lagged by more than 30 seconds.If the load ratios are set incorrectly, or if there is too much loadgenerally, this may lead to a slave permanently hovering around 30seconds lag.If all slaves are lagged by more than 30 seconds, MediaWiki will stopwriting to the database. All edits and other write operations will berefused, with an error returned to the user. This gives the slaves achance to catch up. Before we had this mechanism, the slaves wouldregularly lag by several minutes, making review of recent editsdifficult.In addition to this, MediaWiki attempts to ensure that the user seesevents occurring on the wiki in chronological order. A few seconds of lagcan be tolerated, as long as the user sees a consistent picture fromsubsequent requests. This is done by saving the master binlog positionin the session, and then at the start of each request, waiting for theslave to catch up to that position before doing any reads from it. Ifthis wait times out, reads are allowed anyway, but the request isconsidered to be in "lagged slave mode". Lagged slave mode can bechecked by calling wfGetLB() ->getLaggedSlaveMode(). The onlypractical consequence at present is a warning displayed in the pagefooter.===Lag avoidance===To avoid excessive lag, queries which write large numbers of rows shouldbe split up, generally to write one row at a time. Multi-row INSERT ...SELECT queries are the worst offenders should be avoided altogether.Instead do the select first and then the insert.===Working with lag===Despite our best efforts, it 's not practical to guarantee a low-lagenvironment. Lag will usually be less than one second, but mayoccasionally be up to 30 seconds. For scalability, it 's very importantto keep load on the master low, so simply sending all your queries tothe master is not the answer. So when you have a genuine need forup-to-date data, the following approach is advised:1) Do a quick query to the master for a sequence number or timestamp 2) Run the full query on the slave and check if it matches the data you gotfrom the master 3) If it doesn 't, run the full query on the masterTo avoid swamping the master every time the slaves lag, use of thisapproach should be kept to a minimum. In most cases you should just readfrom the slave and let the user deal with the delay.------------------------------------------------------------------------ Lock contention------------------------------------------------------------------------Due to the high write rate on Wikipedia(and some other wikis), MediaWiki developers need to be very careful to structure their writesto avoid long-lasting locks. By default, MediaWiki opens a transactionat the first query, and commits it before the output is sent. Locks willbe held from the time when the query is done until the commit. So youcan reduce lock time by doing as much processing as possible before youdo your write queries.Often this approach is not good enough, and it becomes necessary toenclose small groups of queries in their own transaction. Use thefollowing syntax:$dbw=wfGetDB(DB_MASTER
Maintenance\addDescription
addDescription( $text)
Set the description text.
Definition: Maintenance.php:291
$maintClass
$maintClass
Definition: updateCollation.php:351
NS_FILE
const NS_FILE
Definition: Defines.php:80
RUN_MAINTENANCE_IF_MAIN
require_once RUN_MAINTENANCE_IF_MAIN
Definition: maintenance.txt:50
page
target page
Definition: All_system_messages.txt:1267
$res
$res
Definition: database.txt:21
Maintenance
Abstract maintenance class for quickly writing and churning out maintenance scripts with minimal effo...
Definition: maintenance.txt:39
UpdateCollation\__construct
__construct()
Default constructor.
Definition: updateCollation.php:43
wfWaitForSlaves
wfWaitForSlaves( $ifWritesSince=null, $wiki=false, $cluster=false, $timeout=null)
Waits for the replica DBs to catch up to the master position.
Definition: GlobalFunctions.php:2966
UpdateCollation\BATCH_SIZE
const BATCH_SIZE
Definition: updateCollation.php:38
php
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
Definition: injection.txt:37
Wikimedia\Rdbms\IDatabase
Basic database interface for live and lazy-loaded relation database handles.
Definition: IDatabase.php:38
$dbr
$dbr
Definition: testCompression.php:50
Collation\singleton
static singleton()
Definition: Collation.php:34
Maintenance\beginTransaction
beginTransaction(IDatabase $dbw, $fname)
Begin a transcation on a DB.
Definition: Maintenance.php:1336
UpdateCollation\getBatchCondition
getBatchCondition( $row, $dbw)
Return an SQL expression selecting rows which sort above the given row, assuming an ordering of cl_co...
Definition: updateCollation.php:254
table
deferred txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user For updating the view updating the linked to tables after a etc PHP does not yet have any way to tell the server to actually return and disconnect while still running these but it might have such a feature in the future We handle these by creating a deferred update object and putting those objects on a global then executing the whole list after the page is displayed We don t do anything smart like collating updates to the same table or such because the list is almost always going to have just one item on if so it s not worth the trouble Since there is a job queue in the jobs table
Definition: deferred.txt:16
Title\newFromRow
static newFromRow( $row)
Make a Title object from a DB row.
Definition: Title.php:464
title
title
Definition: parserTests.txt:219
Maintenance\addOption
addOption( $name, $description, $required=false, $withArg=false, $shortName=false, $multiOccurrence=false)
Add a parameter to the script.
Definition: Maintenance.php:219
$title
namespace and then decline to actually register it file or subcat img or subcat $title
Definition: hooks.txt:964
global
when a variable name is used in a it is silently declared as a new masking the global
Definition: design.txt:95
DB_REPLICA
const DB_REPLICA
Definition: defines.php:25
NS_CATEGORY
const NS_CATEGORY
Definition: Defines.php:88
DB_MASTER
const DB_MASTER
Definition: defines.php:26
will
</td >< td > &</td >< td > t want your writing to be edited mercilessly and redistributed at will
Definition: All_system_messages.txt:914
$options
null means default in associative array with keys and values unescaped Should be merged with default with a value of false meaning to suppress the attribute in associative array with keys and values unescaped & $options
Definition: hooks.txt:2001
UpdateCollation\execute
execute()
Do the actual work.
Definition: updateCollation.php:71
UpdateCollation\updateSortKeySizeHistogram
updateSortKeySizeHistogram( $key)
Definition: updateCollation.php:286
it
=Architecture==Two class hierarchies are used to provide the functionality associated with the different content models:*Content interface(and AbstractContent base class) define functionality that acts on the concrete content of a page, and *ContentHandler base class provides functionality specific to a content model, but not acting on concrete content. The most important function of ContentHandler is to act as a factory for the appropriate implementation of Content. These Content objects are to be used by MediaWiki everywhere, instead of passing page content around as text. All manipulation and analysis of page content must be done via the appropriate methods of the Content object. For each content model, a subclass of ContentHandler has to be registered with $wgContentHandlers. The ContentHandler object for a given content model can be obtained using ContentHandler::getForModelID($id). Also Title, WikiPage and Revision now have getContentHandler() methods for convenience. ContentHandler objects are singletons that provide functionality specific to the content type, but not directly acting on the content of some page. ContentHandler::makeEmptyContent() and ContentHandler::unserializeContent() can be used to create a Content object of the appropriate type. However, it is recommended to instead use WikiPage::getContent() resp. Revision::getContent() to get a page 's content as a Content object. These two methods should be the ONLY way in which page content is accessed. Another important function of ContentHandler objects is to define custom action handlers for a content model, see ContentHandler::getActionOverrides(). This is similar to what WikiPage::getActionOverrides() was already doing.==Serialization==With the ContentHandler facility, page content no longer has to be text based. Objects implementing the Content interface are used to represent and handle the content internally. For storage and data exchange, each content model supports at least one serialization format via ContentHandler::serializeContent($content). The list of supported formats for a given content model can be accessed using ContentHandler::getSupportedFormats(). Content serialization formats are identified using MIME type like strings. The following formats are built in:*text/x-wiki - wikitext *text/javascript - for js pages *text/css - for css pages *text/plain - for future use, e.g. with plain text messages. *text/html - for future use, e.g. with plain html messages. *application/vnd.php.serialized - for future use with the api and for extensions *application/json - for future use with the api, and for use by extensions *application/xml - for future use with the api, and for use by extensions In PHP, use the corresponding CONTENT_FORMAT_XXX constant. Note that when using the API to access page content, especially action=edit, action=parse and action=query &prop=revisions, the model and format of the content should always be handled explicitly. Without that information, interpretation of the provided content is not reliable. The same applies to XML dumps generated via maintenance/dumpBackup.php or Special:Export. Also note that the API will provide encapsulated, serialized content - so if the API was called with format=json, and contentformat is also json(or rather, application/json), the page content is represented as a string containing an escaped json structure. Extensions that use JSON to serialize some types of page content may provide specialized API modules that allow access to that content in a more natural form.==Compatibility==The ContentHandler facility is introduced in a way that should allow all existing code to keep functioning at least for pages that contain wikitext or other text based content. However, a number of functions and hooks have been deprecated in favor of new versions that are aware of the page 's content model, and will now generate warnings when used. Most importantly, the following functions have been deprecated:*Revisions::getText() is deprecated in favor Revisions::getContent() *WikiPage::getText() is deprecated in favor WikiPage::getContent() Also, the old Article::getContent()(which returns text) is superceded by Article::getContentObject(). However, both methods should be avoided since they do not provide clean access to the page 's actual content. For instance, they may return a system message for non-existing pages. Use WikiPage::getContent() instead. Code that relies on a textual representation of the page content should eventually be rewritten. However, ContentHandler::getContentText() provides a stop-gap that can be used to get text for a page. Its behavior is controlled by $wgContentHandlerTextFallback it
Definition: contenthandler.txt:104
UpdateCollation\showSortKeySizeHistogram
showSortKeySizeHistogram()
Definition: updateCollation.php:294
up
static configuration should be added through ResourceLoaderGetConfigVars instead can be used to get the real title after the basic globals have been set up
Definition: hooks.txt:2245
and
and(b) You must cause any modified files to carry prominent notices stating that You changed the files
Maintenance\commitTransaction
commitTransaction(IDatabase $dbw, $fname)
Commit the transcation on a DB handle and wait for replica DBs to catch up.
Definition: Maintenance.php:1351
Maintenance\getOption
getOption( $name, $default=null)
Get an option, or return the default.
Definition: Maintenance.php:254
are
The ContentHandler facility adds support for arbitrary content types on wiki instead of relying on wikitext for everything It was introduced in MediaWiki Each kind of and so on Built in content types are
Definition: contenthandler.txt:9
as
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such as
Definition: distributors.txt:22
Maintenance\getDB
getDB( $db, $groups=[], $wiki=false)
Returns a database to be used by current maintenance script.
Definition: Maintenance.php:1309
Maintenance\output
output( $out, $channel=null)
Throw some output to the user.
Definition: Maintenance.php:388
in
null for the wiki Added in
Definition: hooks.txt:1591
$wgCategoryCollation
$wgCategoryCollation
Specify how category names should be sorted, when listed on a category page.
Definition: DefaultSettings.php:7637
of
globals txt Globals are evil The original MediaWiki code relied on globals for processing context far too often MediaWiki development since then has been a story of slowly moving context out of global variables and into objects Storing processing context in object member variables allows those objects to be reused in a much more flexible way Consider the elegance of
database rows
Definition: globals.txt:10
class
you have access to all of the normal MediaWiki so you can get a DB use the etc For full docs on the Maintenance class
Definition: maintenance.txt:56
Collation\factory
static factory( $collationName)
Definition: Collation.php:48
Maintenance\hasOption
hasOption( $name)
Checks to see if a particular param exists.
Definition: Maintenance.php:240
UpdateCollation\$sizeHistogram
$sizeHistogram
Definition: updateCollation.php:41
UpdateCollation
Maintenance script that will find all rows in the categorylinks table whose collation is out-of-date.
Definition: updateCollation.php:37
$type
$type
Definition: testCompression.php:48