master/php/RevisionFactory_8php_source.html

 <?php
 namespace MediaWiki\Revision;

 use MWException;
 use Title;

 interface RevisionFactory {

     public function newMutableRevisionFromArray( array $fields, $queryFlags = 0, Title $title = null );

     public function newRevisionFromRow( $row, $queryFlags = 0, Title $title = null );

     public function newRevisionFromArchiveRow(
         $row,
         $queryFlags = 0,
         Title $title = null,
         array $overrides = []
     );

 }

 class_alias( RevisionFactory::class, 'MediaWiki\Storage\RevisionFactory' );
array
The wiki should then use memcached to cache various data To use multiple just add more items to the array To increase the weight of a make its entry a array("192.168.0.1:11211", 2))

Revision\RevisionFactory\newRevisionFromArchiveRow
newRevisionFromArchiveRow( $row, $queryFlags=0, Title $title=null, array $overrides=[])
Make a fake revision object from an archive table row.

use
Apache License January AND DISTRIBUTION Definitions License shall mean the terms and conditions for use
Definition: APACHE-LICENSE-2.0.txt:3

MediaWiki\Revision
Created by PhpStorm.
Definition: FallbackSlotRoleHandler.php:23

null
this hook is for auditing only or null if authentication failed before getting that far or null if we can t even determine that When $user is not null
Definition: hooks.txt:780

$title
namespace and then decline to actually register it file or subcat img or subcat $title
Definition: hooks.txt:925

Revision\RevisionFactory\newMutableRevisionFromArray
newMutableRevisionFromArray(array $fields, $queryFlags=0, Title $title=null)
Constructs a new RevisionRecord based on the given associative array following the MW1...

Revision\RevisionFactory
Service for constructing revision objects.
Definition: RevisionFactory.php:37

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:35

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:52

Revision\RevisionFactory\newRevisionFromRow
newRevisionFromRow( $row, $queryFlags=0, Title $title=null)
Constructs a RevisionRecord given a database row and content slots.

Title

MWException