MediaWiki  master
deleteArchivedRevisions.php
Go to the documentation of this file.
1 <?php
26 require_once __DIR__ . '/Maintenance.php';
27 
35  public function __construct() {
36  parent::__construct();
37  $this->addDescription(
38  "Deletes all archived revisions\nThese revisions will no longer be restorable" );
39  $this->addOption( 'delete', 'Performs the deletion' );
40  }
41 
42  public function execute() {
43  $dbw = $this->getDB( DB_MASTER );
44 
45  if ( !$this->hasOption( 'delete' ) ) {
46  $count = $dbw->selectField( 'archive', 'COUNT(*)', '', __METHOD__ );
47  $this->output( "Found $count revisions to delete.\n" );
48  $this->output( "Please run the script again with the --delete option "
49  . "to really delete the revisions.\n" );
50  return;
51  }
52 
53  $this->output( "Deleting archived revisions... " );
54  $dbw->delete( 'archive', '*', __METHOD__ );
55  $count = $dbw->affectedRows();
56  $this->output( "done. $count revisions deleted.\n" );
57 
58  if ( $count ) {
59  $this->purgeRedundantText( true );
60  }
61  }
62 }
63 
65 require_once RUN_MAINTENANCE_IF_MAIN;
Abstract maintenance class for quickly writing and churning out maintenance scripts with minimal effo...
Definition: maintenance.txt:39
hasOption( $name)
Checks to see if a particular option exists.
require_once RUN_MAINTENANCE_IF_MAIN
Definition: maintenance.txt:50
const DB_MASTER
Definition: defines.php:26
addDescription( $text)
Set the description text.
Maintenance script to delete archived (deleted from public) revisions from the database.
getDB( $db, $groups=[], $wiki=false)
Returns a database to be used by current maintenance script.
output( $out, $channel=null)
Throw some output to the user.
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:35
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:52
addOption( $name, $description, $required=false, $withArg=false, $shortName=false, $multiOccurrence=false)
Add a parameter to the script.
purgeRedundantText( $delete=true)
Support function for cleaning up redundant text records.