MediaWiki  1.32.5
DBAccessBase.php
Go to the documentation of this file.
1 <?php
2 
3 use MediaWiki\MediaWikiServices;
4 use Wikimedia\Rdbms\IDatabase;
5 use Wikimedia\Rdbms\LoadBalancer;
6 
34 abstract class DBAccessBase implements IDBAccessObject {
39  protected $wiki = false;
40 
45  public function __construct( $wiki = false ) {
46  $this->wiki = $wiki;
47  }
48 
62  protected function getConnection( $id, $groups = [] ) {
63  $loadBalancer = $this->getLoadBalancer();
64 
65  return $loadBalancer->getConnection( $id, $groups, $this->wiki );
66  }
67 
77  protected function releaseConnection( IDatabase $db ) {
78  if ( $this->wiki !== false ) {
79  $loadBalancer = $this->getLoadBalancer();
80  $loadBalancer->reuseConnection( $db );
81  }
82  }
83 
93  public function getLoadBalancer() {
94  $lbFactory = MediaWikiServices::getInstance()->getDBLoadBalancerFactory();
95  return $lbFactory->getMainLB( $this->wiki );
96  }
97 }
wiki
Prior to maintenance scripts were a hodgepodge of code that had no cohesion or formal method of action Beginning maintenance scripts have been cleaned up to use a unified class Directory structure How to run a script How to write your own DIRECTORY STRUCTURE The maintenance directory of a MediaWiki installation contains several all of which have unique purposes HOW TO RUN A SCRIPT Ridiculously just call php someScript php that s in the top level maintenance directory if not default wiki
Definition: maintenance.txt:1
DBAccessBase\releaseConnection
releaseConnection(IDatabase $db)
Releases a database connection and makes it available for recycling.
Definition: DBAccessBase.php:77
IDBAccessObject
Interface for database access objects.
Definition: IDBAccessObject.php:55
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
Wikimedia\Rdbms\IDatabase
Basic database interface for live and lazy-loaded relation database handles.
Definition: IDatabase.php:38
use
as see the revision history and available at free of to any person obtaining a copy of this software and associated documentation to deal in the Software without including without limitation the rights to use
Definition: MIT-LICENSE.txt:10
DBAccessBase\getConnection
getConnection( $id, $groups=[])
Returns a database connection.
Definition: DBAccessBase.php:62
Wikimedia\Rdbms\LoadBalancer
Database connection, tracking, load balancing, and transaction manager for a cluster.
Definition: LoadBalancer.php:41
DBAccessBase
Definition: DBAccessBase.php:34
DBAccessBase\getLoadBalancer
getLoadBalancer()
Get the database type used for read operations.
Definition: DBAccessBase.php:93
MediaWikiServices
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 MediaWikiServices
Definition: injection.txt:23
DBAccessBase\$wiki
$wiki
Definition: DBAccessBase.php:39
DBAccessBase\__construct
__construct( $wiki=false)
Definition: DBAccessBase.php:45