$wgActorTableSchemaMigrationStage indicates the Actor migration stage. Most wikis can set this to SCHEMA_COMPAT_NEW and run maintenance/migrateActors.php as soon as any necessary extensions are updated.
Note that reading the old and new schema at the same time is not supported in 1.32, but was (with significant query performance issues) in 1.31.
MediaWiki 1.37-1.38[edit] MediaWiki versions:1.37 – 1.38
The recommended values are:
SCHEMA_COMPAT_TEMP (0x30)SCHEMA_COMPAT_WRITE_TEMP_AND_NEW | SCHEMA_COMPAT_READ_TEMP (0x130)SCHEMA_COMPAT_WRITE_TEMP_AND_NEW | SCHEMA_COMPAT_READ_NEW (0x310)SCHEMA_COMPAT_NEW (0x300)1.32 – 1.34
$wgActorTableSchemaMigrationStage can be set to one combination of the Schema change migration flags.
The allowed values for the configuration are one of the SCHEMA_COMPAT_* constants. The recommended values are:
SCHEMA_COMPAT_OLD (0x03, default value) - Only read and write the old schema. The new schema need not even exist. This is used from when the patch is merged until the schema change is actually applied to the database.SCHEMA_COMPAT_WRITE_BOTH | SCHEMA_COMPAT_READ_OLD (0x13) - Write both the old and new schema. Read the old schema. This is used while the change is being tested, allowing easy roll-back to the old schema.SCHEMA_COMPAT_WRITE_BOTH | SCHEMA_COMPAT_READ_NEW (0x31) - Write both the old and new schema. Read the new schema. This is used while the change is being tested, after running migrateActors.php, allowing easy roll-back to the old schema.SCHEMA_COMPAT_NEW (0x30) - Only read and write the new schema. The old schema (and the feature flag) may now be removed.$wgActorTableSchemaMigrationStage can be set to one of the Schema change migration flags. The allowed value range for the configuration is one of the MIGRATION_* constants. The available constants and their planned use cases on Wikimedia Foundation wikis are as follows:
MIGRATION_OLD (0, default value) - Only read and write the old schema. The new schema need not even exist. This is used from when the patch is merged until the schema change is actually applied to the database.MIGRATION_WRITE_BOTH (1) - Write both the old and new schema. Read the new schema preferentially, falling back to the old. This is used while the change is being tested, allowing easy roll-back to the old schema.MIGRATION_WRITE_NEW (2) - Write only the new schema. Read the new schema preferentially, falling back to the old. This is used while running the maintenance script to migrate existing entries in the old schema to the new schema.MIGRATION_NEW (3) - Only read and write the new schema. The old schema (and the feature flag) may now be removed.RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4