Manual:$wgCommentTableSchemaMigrationStage/ja
| File:OOjs UI icon alert-destructive.svg | <translate> This feature was removed completely in version <tvar name=ver>1.33.0</tvar>.</translate> |
| <translate> Miscellaneous settings</translate>: $wgCommentTableSchemaMigrationStage | |
|---|---|
comment テーブル スキーマ移行の段階。 |
|
| <translate> Introduced in version:</translate> | 1.30.0 (Gerrit change 357892; git #Ic3a434c) |
| <translate> Removed in version:</translate> | 1.33.0 (Gerrit change 482371; git #0abb9338) |
| <translate> Allowed values:</translate> | 下記参照 |
| <translate> Default value:</translate> | MIGRATION_OLD |
| <translate> Other settings:</translate> <translate> Alphabetical</translate> | <translate> By function</translate> | |
$wgCommentTableSchemaMigrationStage は comment テーブル スキーマ移行の段階を示します。
Most wikis can set this to MIGRATION_NEW and run maintenance/migrateComments.php as soon as any necessary extensions are updated.
詳細
$wgCommentTableSchemaMigrationStage 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) - 古いスキーマのみを読み書きします。 新しいスキーマが存在する必要すらありません。 This is used from when the patch is merged until the schema change is actually applied to the database.MIGRATION_WRITE_BOTH(1) - 新旧両方のスキーマに書き込みます。 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) - 新しいスキーマのみに書き込みます。 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) - 新しいスキーマのみを読み書きします。 旧スキーマ (および機能フラグ) は除去できる場合があります。
For non-Wikimedia Foundation wikis it is recommended to set this to MIGRATION_NEW and to run maintenance/migrateComments.php in order to take advantage of the new schema.
$wgForeignFileRepos
If you operate a wiki farm using $wgForeignFileRepos with ForeignDBRepo or ForeignDBViaLBRepo, it is important to keep in mind that client and repository wiki must be in nearby migration stages.
(T181930 を参照)
| 外部リポジトリのウィキ | |||||||
|---|---|---|---|---|---|---|---|
| スキーマ変更なし | OLD | WRITE_BOTH | WRITE_NEW | NEW | フィールドの削除 | ||
| クライアント ウィキ | スキーマ変更なし | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> No</translate> | <translate> No</translate> | <translate> No</translate> |
| OLD | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> No</translate> | <translate> No</translate> | <translate> No</translate> | |
| WRITE_BOTH | <translate> No</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> No</translate> | |
| WRITE_NEW | <translate> No</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> No</translate> | |
| NEW | <translate> No</translate> | <translate> No</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | |
| フィールドの削除 | <translate> No</translate> | <translate> No</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | <translate> Yes</translate> | |
