Status: | effective |
Progress: | 100% |
Version: | 3.2.0+ |
Help:Maintenance script setupStore.php
(Redirected from Help:Maintenance script "setupStore.php")
MediaWiki file: Maintenance script setupStore.php | |
---|---|
Location: | /maintenance/ |
Source code: | script setupStore.php master • script setupStore.php 1.41.1 • script setupStore.php 1.40.3 • script setupStore.php 1.39.7 |
Classes: | script setupStore.php Find code • script setupStore.php Find documentation |
maintenance script that sets up the storage backend currently selected in the "LocalSettings.php" file or the default data backend (store) if no other backend was selected. Semantic MediaWiki 3.2.0Released on an unknown date unknown versions of MediaWiki brought an improved client output to this maintenance script.1 Moreover this maintenance script now checks if the minimum requirements for the version of the selected data store is met by the respective server's environment.2
The "setupStore.php" script is aUsage
php setupStore.php [--delete|--backend|--nochecks|--skip-optimize|--skip-import] [backend]
Parameters
Maintenance scripts provide generic maintenance parameters, script dependent parameters and depending on the maintenance script script specific parameters which are described on this page if provided.
- Script specific parameters
Parameter | Description |
---|---|
--delete
|
Delete all semantic data, uninstall the selected storage backend. This is useful when moving to a new storage engine, and in the rare case of unsinstalling Semantic MediaWiki. Deleted data can be recreated using this script (setup) followed by maintenance script "rebuildData.php"No description was provided. (rebuild) but this may take some time. |
--backend [backend]
|
Execute the operation for the storage backend of the given name. For instance "SMWSQLStore3" or "SMWSQLStore2". |
--nochecks
|
When specified, no prompts are provided. Deletion will thus happen without the need to provide any confirmation. |
--skip-optimize 3
|
When specified the key distribution is not being analyzed, optimized and stored. Thus the internal query planner cannot determine the most efficient execution for queries. |
--skip-import 3
|
When specified, the import process of default or custom vocabularies is not being done. |
Examples
Note
This maintenance script is by default performing a database optimization if not skipped with the --skip-optimize
flag. If this was not done within the period of 90 days a maintenance alert will be added to the Semantic MediaWiki dashboard reminding of this task. The last database optimization run is recorded by this maintenance script by adding the last runs timestamp to the last_optimization_run
information of the setup information file (".smw.json").4
See also
- Help page on maintenance script "update.php" (MediaWiki.org)
- Help page on maintenance script "populateHashField.php"No description was provided.
- Help page on maintenance script "updateEntityCountMap.php"No description was provided.
- Help page on importing vocabulary
- Help page on importing contents
- Help page on the setup check
- Help page on the setup information file (".smw.json")