MediaWiki REL1_28
Go to the documentation of this file.
29class ActivityUpdateJob extends Job {
31 parent::__construct( 'activityUpdateJob', $title, $params );
33 if ( !isset( $params['type'] ) ) {
34 throw new InvalidArgumentException( "Missing 'type' parameter." );
35 }
37 $this->removeDuplicates = true;
38 }
40 public function run() {
41 if ( $this->params['type'] === 'updateWatchlistNotification' ) {
43 } else {
44 throw new InvalidArgumentException(
45 "Invalid 'type' parameter '{$this->params['type']}'." );
46 }
48 return true;
49 }
51 protected function updateWatchlistNotification() {
52 $casTimestamp = ( $this->params['notifTime'] !== null )
53 ? $this->params['notifTime']
54 : $this->params['curTime'];
56 $dbw = wfGetDB( DB_MASTER );
57 $dbw->update( 'watchlist',
58 [
59 'wl_notificationtimestamp' => $dbw->timestampOrNull( $this->params['notifTime'] )
60 ],
61 [
62 'wl_user' => $this->params['userid'],
63 'wl_namespace' => $this->title->getNamespace(),
64 'wl_title' => $this->title->getDBkey(),
65 // Add a "check and set" style comparison to handle conflicts.
66 // The inequality always avoids updates when the current value
67 // is already NULL per ANSI SQL. This is desired since NULL means
68 // that the user is "caught up" on edits already. When the field
69 // is non-NULL, make sure not to set it back in time or set it to
70 // NULL when newer revisions were in fact added to the page.
71 'wl_notificationtimestamp < ' . $dbw->addQuotes( $dbw->timestamp( $casTimestamp ) )
72 ],
73 __METHOD__
74 );
75 }
wfGetDB( $db, $groups=[], $wiki=false)
Get a Database object.
Job for updating user activity like "last viewed" timestamps.
__construct(Title $title, array $params)
Class to both describe a background job and handle jobs.
Definition Job.php:31
Title $title
Definition Job.php:42
array $params
Array of job parameters.
Definition Job.php:36
Represents a title within MediaWiki.
Definition Title.php:36
the array() calling protocol came about after MediaWiki 1.4rc1.
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
Definition defines.php:23