Status: | effective |
Progress: | 100% |
Version: | 3.2.0+ |
Maintenance script "setupStore.php"
setupStore.php | |
---|---|
Allows to set up the data backend/store | |
Further Information | |
Provided by: | Semantic MediaWiki |
Added: | 2.0.0 |
Removed: | still in use |
Location (path): | ./extensions/SemanticMediaWiki/maintenance/ |
Table of Contents | |
Contents |
The "setupStore.php" script is a 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 7 September 2020 and compatible with MW 1.31.0 - 1.35.x. 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
Usage[edit]
php setupStore.php [--delete|--backend|--nochecks|--skip-optimize|--skip-import] [backend]
Parameters[edit]
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"Allows to rebuild all the semantic data for a selected data backend/store (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[edit]
- Maintenance script "setupStore.php" example (no parameter)
- Maintenance script "setupStore.php" example (--skip-optimize parameter)
- Maintenance script "setupStore.php" example (--skip-import parameter)
- Maintenance script "setupStore.php" example (--delete parameter)
Note[edit]
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[edit]
- Help page on maintenance script "update.php" (MediaWiki.org)
- Help page on maintenance script "populateHashField.php"Allows to do mass populating of database field "smw_hash" when initially upgrading to Semantic MediaWiki 3.0.1 and later
- Help page on maintenance script "updateEntityCountMap.php"Allows to do mass populating of database field "smw_countmap" when initially upgrading to Semantic MediaWiki 3.2.0 and later
- 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")
References
- ^ Semantic MediaWiki: GitHub pull request gh:smw:4403
- ^ Semantic MediaWiki: GitHub pull request gh:smw:4461
- a b Semantic MediaWiki: GitHub pull request gh:smw:2801
- ^ Semantic MediaWiki: GitHub pull request gh:smw:4476