Thijs/wiki.techinc.nl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
wiki.techinc.nl/includes/installer/SqliteUpdater.php

261 lines
14 KiB
PHP
Raw Normal View History

* Split Mysql/Sqlite updates into their own files * Rename Update -> DatabaseUpdaters to be more consistent with DatabaseInstaller * Made DatabaseUpdaters abstract and merged the Updaters interface in, had Mysql/Oracle/Sqlite subclass it. Entry point is now factory DatabaseUpdaters::newForDB()
2010-07-20 22:28:50 +00:00
<?php
* Added file description headers * Added @file where needed
2010-08-21 18:20:09 +00:00
/**
* Sqlite-specific updater.
*
Added missing GPLv2 headers in some places. Also made file/class documentation more consistent. Change-Id: I1615bf268515ed7169e33173cea6ec30402451dc
2012-05-06 05:50:15 +00:00
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License along
* with this program; if not, write to the Free Software Foundation, Inc.,
* 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
* http://www.gnu.org/copyleft/gpl.html
*
* Added file description headers * Added @file where needed
2010-08-21 18:20:09 +00:00
* @file
installer: Rename Doxygen group from "Deployment" to "Installer" Also improve the description a bit and explain at a high level how this code is used, and which classes back those entry points. Change-Id: Ia69531858e714d0b43a29a7d5b6dcc5c7edd8240
2019-11-25 23:24:49 +00:00
* @ingroup Installer
* Added file description headers * Added @file where needed
2010-08-21 18:20:09 +00:00
*/
Removing trailing whitespace
2010-12-16 11:20:39 +00:00
* Split Mysql/Sqlite updates into their own files * Rename Update -> DatabaseUpdaters to be more consistent with DatabaseInstaller * Made DatabaseUpdaters abstract and merged the Updaters interface in, had Mysql/Oracle/Sqlite subclass it. Entry point is now factory DatabaseUpdaters::newForDB()
2010-07-20 22:28:50 +00:00
/**
Added deployment documentation group
2010-07-29 18:36:39 +00:00
* Class for handling updates to Sqlite databases.
Removing trailing whitespace
2010-12-16 11:20:39 +00:00
*
installer: Rename Doxygen group from "Deployment" to "Installer" Also improve the description a bit and explain at a high level how this code is used, and which classes back those entry points. Change-Id: Ia69531858e714d0b43a29a7d5b6dcc5c7edd8240
2019-11-25 23:24:49 +00:00
* @ingroup Installer
Added deployment documentation group
2010-07-29 18:36:39 +00:00
* @since 1.17
Remove ipb_anon_only from ipb_address_unique UNIQUE INDEX Bug: T251188 Change-Id: I4618f659be64134664ac1644de2b51d74f000e4c
2020-05-04 20:16:03 +00:00
* @property Wikimedia\Rdbms\DatabaseSqlite $db
* Split Mysql/Sqlite updates into their own files * Rename Update -> DatabaseUpdaters to be more consistent with DatabaseInstaller * Made DatabaseUpdaters abstract and merged the Updaters interface in, had Mysql/Oracle/Sqlite subclass it. Entry point is now factory DatabaseUpdaters::newForDB()
2010-07-20 22:28:50 +00:00
*/
class SqliteUpdater extends DatabaseUpdater {
Removing trailing whitespace
2010-12-16 11:20:39 +00:00
* Split Mysql/Sqlite updates into their own files * Rename Update -> DatabaseUpdaters to be more consistent with DatabaseInstaller * Made DatabaseUpdaters abstract and merged the Updaters interface in, had Mysql/Oracle/Sqlite subclass it. Entry point is now factory DatabaseUpdaters::newForDB()
2010-07-20 22:28:50 +00:00
protected function getCoreUpdateList() {
Convert all array() syntax to [] Per wikitech-l consensus: https://lists.wikimedia.org/pipermail/wikitech-l/2016-February/084821.html Notes: * Disabled CallTimePassByReference due to false positives (T127163) Change-Id: I2c8ce713ce6600a0bb7bf67537c87044c7a45c4b
2016-02-17 09:09:32 +00:00
return [
Add rc_name_type_patrolled_timestamp index Bug: T140108 Change-Id: I382a5f0daef703a3d16fe008a5e1d1402f2c7b33
2016-07-14 16:01:04 +00:00
// 1.28
[ 'addIndex', 'recentchanges', 'rc_name_type_patrolled_timestamp',
'patch-add-rc_name_type_patrolled_timestamp_index.sql' ],
Add primary key to change_tag and tag_summary tables Based heavily on 43e386ca16411096bbbd7f14f9f4e15c5e268fe7. Bug: T123225 Change-Id: I33480f4016812259700979f1145099744bb451d4
2016-08-13 01:06:33 +00:00
[ 'addField', 'change_tag', 'ct_id', 'patch-change_tag-ct_id.sql' ],
Add externallinks.el_index_60 column and indexes This will allow for replacing the limit-and-offset queries with queries that page in a sensible manner. Bug: T59176 Change-Id: If5c137f68496772f3fff3a735b7b0c388426e518
2016-11-18 19:54:28 +00:00
// 1.29
[ 'addField', 'externallinks', 'el_index_60', 'patch-externallinks-el_index_60.sql' ],
User group memberships that expire This patch adds an ug_expiry column to the user_groups table, a timestamp giving a date when the user group expires. A new UserGroupMembership class, based on the Block class, manages entries in this table. When the expiry date passes, the row in user_groups is ignored, and will eventually be purged from the DB when UserGroupMembership::insert is next called. Old, expired user group memberships are not kept; instead, the log entries are available to find the history of these memberships, similar to the way it has always worked for blocks and protections. Anyone getting user group info through the User object will get correct information. However, code that reads the user_groups table directly will now need to skip over rows with ug_expiry < wfTimestampNow(). See UsersPager for an example of how to do this. NULL is used to represent infinite (no) expiry, rather than a string 'infinity' or similar (except in the API). This allows existing user group assignments and log entries, which are all infinite in duration, to be treated the same as new, infinite-length memberships, without special casing everything. The whole thing is behind the temporary feature flag $wgDisableUserGroupExpiry, in accordance with the WMF schema change policy. The opportunity has been taken to refactor some static user-group-related functions out of User into UserGroupMembership, and also to add a primary key (ug_user, ug_group) to the user_groups table. There are a few breaking changes: - UserRightsProxy-like objects are now required to have a getGroupMemberships() function. - $user->mGroups (on a User object) is no longer present. - Some protected functions in UsersPager are altered or removed. - The UsersPagerDoBatchLookups hook (unused in any Wikimedia Git-hosted extension) has a change of parameter. Bug: T12493 Depends-On: Ia9616e1e35184fed9058d2d39afbe1038f56d7fa Depends-On: I86eb1d5619347ce54a5f33a591417742ebe5d6f8 Change-Id: I93c955dc7a970f78e32aa503c01c67da30971d1a
2017-01-12 06:07:56 +00:00
[ 'addField', 'user_groups', 'ug_expiry', 'patch-user_groups-ug_expiry.sql' ],
Alter `revision` for actor, comment, and MCR We're finally to the point of making the massive alter to the `revision` table that we've been building up to for 2.5 years now. Changes here are: * Drop `rev_text_id`, `rev_content_model`, and `rev_content_format` that MCR obsoleted. * Drop `ar_text_id`, `ar_content_model`, and `ar_content_format` that MCR obsoleted. * Replace `rev_comment` with `rev_comment_id`. * Replace `rev_user` and `rev_user_text` with `rev_actor`, plus associated index changes. Future patches will make the code changes to migrate data from `revision_actor_temp` and `revision_comment_temp` into the new `revision` columns. Bug: T251343 Bug: T184615 Bug: T215466 Change-Id: I18071a2fe45907a0cf1b0fefebd96a97a2dacb7b
2019-11-21 20:47:13 +00:00
[ 'ifTableNotExists', 'actor',
'addIndex', 'image', 'img_user_timestamp', 'patch-image-user-index-2.sql' ],
Follow-up to '3D' file type addition Based on feedback on Id78a504302fa664b353a4c45bdc5d99f95a0180a Bug: T157348 Change-Id: Id6bfe8d20307f62e4673a5ef30e79f164b1ea034
2017-07-20 14:43:50 +00:00
// 1.30
[ 'modifyField', 'image', 'img_media_type', 'patch-add-3d.sql' ],
Create new table to be used for querying IP ranges. When revisions by logged out users are created, they will get copied to this table. We can then JOIN it with revision when querying for ranges at Special:Contributions. DBA approval for this table can be found at T156318 Bug: T163562 Change-Id: I6593eb13701128faa782691a6b25ec01869c827d
2017-08-09 21:34:09 +00:00
[ 'addTable', 'ip_changes', 'patch-ip_changes.sql' ],
Convert UNIQUE keys into PRIMARY KEY WMF DBAs have been doing a massive effort to convert UNIQUE KEYS into PRIMARY KEY. Having a PK is essential to do maintenance, specially on large tasks. By not having a PK it is impossible to add it in a safe way if not done directly on the master. Having a PK means that we can easily change the PK into another one if needed in the future. The ones we chose might not be the best ones, but will allow us to get them changed. Bug: T172514 Change-Id: Id635297838938c7c5dfe65d45285a4d16d65152d
2017-08-04 12:43:50 +00:00
[ 'renameIndex', 'categorylinks', 'cl_from', 'PRIMARY', false,
'patch-categorylinks-fix-pk.sql' ],
[ 'renameIndex', 'templatelinks', 'tl_from', 'PRIMARY', false,
'patch-templatelinks-fix-pk.sql' ],
[ 'renameIndex', 'pagelinks', 'pl_from', 'PRIMARY', false, 'patch-pagelinks-fix-pk.sql' ],
[ 'renameIndex', 'text', 'old_id', 'PRIMARY', false, 'patch-text-fix-pk.sql' ],
[ 'renameIndex', 'imagelinks', 'il_from', 'PRIMARY', false, 'patch-imagelinks-fix-pk.sql' ],
[ 'renameIndex', 'iwlinks', 'iwl_from', 'PRIMARY', false, 'patch-iwlinks-fix-pk.sql' ],
[ 'renameIndex', 'langlinks', 'll_from', 'PRIMARY', false, 'patch-langlinks-fix-pk.sql' ],
[ 'renameIndex', 'log_search', 'ls_field_val', 'PRIMARY', false, 'patch-log_search-fix-pk.sql' ],
[ 'renameIndex', 'module_deps', 'md_module_skin', 'PRIMARY', false,
'patch-module_deps-fix-pk.sql' ],
[ 'renameIndex', 'objectcache', 'keyname', 'PRIMARY', false, 'patch-objectcache-fix-pk.sql' ],
[ 'renameIndex', 'querycache_info', 'qci_type', 'PRIMARY', false,
'patch-querycache_info-fix-pk.sql' ],
[ 'renameIndex', 'site_stats', 'ss_row_id', 'PRIMARY', false, 'patch-site_stats-fix-pk.sql' ],
[ 'renameIndex', 'user_former_groups', 'ufg_user_group', 'PRIMARY', false,
'patch-user_former_groups-fix-pk.sql' ],
[ 'renameIndex', 'user_properties', 'user_properties_user_property', 'PRIMARY', false,
'patch-user_properties-fix-pk.sql' ],
Add `comment` table and code to start using it A subsequent patch will remove the old columns. Bug: T166732 Change-Id: Ic3a434c061ed6e443ea072bc62dda09acbeeed7f
2017-06-06 17:39:14 +00:00
[ 'addTable', 'comment', 'patch-comment-table.sql' ],
Split down patch-comment-table.sql Bug: T227662 Change-Id: I7617616df57f7468d06e9b52426b6851bfef0e7d
2019-08-15 13:36:53 +00:00
[ 'addTable', 'revision_comment_temp', 'patch-revision_comment_temp-table.sql' ],
[ 'addField', 'archive', 'ar_comment_id', 'patch-archive-ar_comment_id.sql' ],
Fix double dot in filename Follows-Up: I7617616df57f7468d06e9b52426b6851bfef0e7d Change-Id: Ia8be2fd6a13d095e27a6489b0126763573dd6194
2019-09-27 16:22:11 +00:00
[ 'modifyField', 'image', 'img_description', 'patch-image-img_description-default.sql' ],
Split down patch-comment-table.sql Bug: T227662 Change-Id: I7617616df57f7468d06e9b52426b6851bfef0e7d
2019-08-15 13:36:53 +00:00
[ 'addField', 'ipblocks', 'ipb_reason_id', 'patch-ipblocks-ipb_reason_id.sql' ],
[ 'addField', 'logging', 'log_comment_id', 'patch-logging-log_comment_id.sql' ],
[ 'addField', 'oldimage', 'oi_description_id', 'patch-oldimage-oi_description_id.sql' ],
[ 'addField', 'protected_titles', 'pt_reason_id', 'patch-protected_titles-pt_reason_id.sql' ],
[ 'addField', 'recentchanges', 'rc_comment_id', 'patch-recentchanges-rc_comment_id.sql' ],
[ 'modifyField', 'revision', 'rev_comment', 'patch-revision-rev_comment-default.sql' ],
DB: Add img_description_id column This begins the process of merging image_comment_temp into the image table by adding the needed column. Iab5f5215 will adjust the code to use it and to add the necessary migration script. Note this patch puts the new schema change in the 1.30 section rather than the 1.31 section. This allows Iab5f5215 to have migrateComments.php migrate the comments directly to the new field instead of having to populate and then depopulate the temporary table. Bug: T188132 Change-Id: I2485c5a758bf03bb2b4991eea920abd9d0d30bda
2018-03-07 15:40:27 +00:00
// This field was added in 1.31, but is put here so it can be used by 'migrateComments'
[ 'addField', 'image', 'img_description_id', 'patch-image-img_description_id.sql' ],
SQLite: Split actor and comment filearchive updates to a separate file On a fresh install, update.php will apply patch-editsummary-length.sql even though it doesn't need to. But this partially wipes out the new schema from tables.sql, and the omnibus comment and actor table patches don't detect this, leading to filearchive missing the new fields. Unlike the case with patch-add-3d.sql in I335cb8d9, here the patch does make a change (if only a tiny one): fa_deleted_reason changes from TEXT to BLOB. Change-Id: I08047ff1207d471660365c0eb3faabc0b47746bb
2018-11-28 18:53:17 +00:00
[ 'addField', 'filearchive', 'fa_description_id', 'patch-filearchive-fa_description_id.sql' ],
DB: Add img_description_id column This begins the process of merging image_comment_temp into the image table by adding the needed column. Iab5f5215 will adjust the code to use it and to add the necessary migration script. Note this patch puts the new schema change in the 1.30 section rather than the 1.31 section. This allows Iab5f5215 to have migrateComments.php migrate the comments directly to the new field instead of having to populate and then depopulate the temporary table. Bug: T188132 Change-Id: I2485c5a758bf03bb2b4991eea920abd9d0d30bda
2018-03-07 15:40:27 +00:00
Add `comment` table and code to start using it A subsequent patch will remove the old columns. Bug: T166732 Change-Id: Ic3a434c061ed6e443ea072bc62dda09acbeeed7f
2017-06-06 17:39:14 +00:00
[ 'migrateComments' ],
Convert INDEX into PRIMARY KEY in l10n_cache Bug: T146591 Change-Id: I85ab18bfa30e562e76253e3ef71653dbf46db041
2016-10-28 14:33:32 +00:00
[ 'renameIndex', 'l10n_cache', 'lc_lang_key', 'PRIMARY', false,
'patch-l10n_cache-primary-key.sql' ],
MCR database schema Schema additions/updates for MySQL, SQLite, PostgreSQL, MSSQL and Oracle to add new tables: * content * content_models * slots * slot_roles See also https://www.mediawiki.org/wiki/Multi-Content_Revisions/Database_Schema Bug: T174028 Change-Id: I30a3a9834d54d0e6957553d91908b2b73b2c802f
2017-09-18 15:00:26 +00:00
// 1.31
[ 'addTable', 'content', 'patch-content.sql' ],
[ 'addTable', 'content_models', 'patch-content_models.sql' ],
[ 'addTable', 'slots', 'patch-slots.sql' ],
MCR: replace slot_inherited with slot_origin Bug: T189004 Change-Id: Ie9dbda3296a71f584c82a5f275098adc225a53d5
2018-03-06 14:42:43 +00:00
[ 'addField', 'slots', 'slot_origin', 'patch-slot-origin.sql' ],
Migrate ar_text to modern storage This really should have been done a very long time ago. This adds a maintenance script to migrate rows with ar_text_id null to modern storage, either the text table or ExternalStore. Bug: T36925 Change-Id: I5608c6b6d3ecad516b785e13d668427c1b762e41
2017-11-28 21:13:09 +00:00
[ 'addTable', 'slot_roles', 'patch-slot_roles.sql' ],
[ 'migrateArchiveText' ],
Add `actor` table and code to start using it Storing the user name or IP in every row in large tables like revision and logging takes up space and makes operations on these tables slower. This patch begins the process of moving those into one "actor" table which other tables can reference with a single integer field. A subsequent patch will remove the old columns. Bug: T167246 Depends-On: I9293fd6e0f958d87e52965de925046f1bb8f8a50 Change-Id: I8d825eb02c69cc66d90bd41325133fd3f99f0226
2017-09-12 17:12:29 +00:00
[ 'addTable', 'actor', 'patch-actor-table.sql' ],
Split down patch-actor-table.sql Bug: T227662 Change-Id: I024ff1d6f4c2726242138ba7e7f19480d9d2b948
2019-09-28 14:48:19 +00:00
[ 'addField', 'archive', 'ar_actor', 'patch-archive-ar_actor.sql' ],
[ 'addTable', 'revision_actor_temp', 'patch-revision_actor_temp-table.sql' ],
[ 'addField', 'ipblocks', 'ipb_by_actor', 'patch-ipblocks-ipb_by_actor.sql' ],
[ 'addField', 'image', 'img_actor', 'patch-image-img_actor.sql' ],
[ 'addField', 'oldimage', 'oi_actor', 'patch-oldimage-oi_actor.sql' ],
SQLite: Split actor and comment filearchive updates to a separate file On a fresh install, update.php will apply patch-editsummary-length.sql even though it doesn't need to. But this partially wipes out the new schema from tables.sql, and the omnibus comment and actor table patches don't detect this, leading to filearchive missing the new fields. Unlike the case with patch-add-3d.sql in I335cb8d9, here the patch does make a change (if only a tiny one): fa_deleted_reason changes from TEXT to BLOB. Change-Id: I08047ff1207d471660365c0eb3faabc0b47746bb
2018-11-28 18:53:17 +00:00
[ 'addField', 'filearchive', 'fa_actor', 'patch-filearchive-fa_actor.sql' ],
Split down patch-actor-table.sql Bug: T227662 Change-Id: I024ff1d6f4c2726242138ba7e7f19480d9d2b948
2019-09-28 14:48:19 +00:00
[ 'addField', 'recentchanges', 'rc_actor', 'patch-recentchanges-rc_actor.sql' ],
[ 'addField', 'logging', 'log_actor', 'patch-logging-log_actor.sql' ],
Add `actor` table and code to start using it Storing the user name or IP in every row in large tables like revision and logging takes up space and makes operations on these tables slower. This patch begins the process of moving those into one "actor" table which other tables can reference with a single integer field. A subsequent patch will remove the old columns. Bug: T167246 Depends-On: I9293fd6e0f958d87e52965de925046f1bb8f8a50 Change-Id: I8d825eb02c69cc66d90bd41325133fd3f99f0226
2017-09-12 17:12:29 +00:00
[ 'migrateActors' ],
Add default for revision.rev_text_id where missing This adds a default of 0 for: - Mssql - Mysql - Sqlite The field is already NULLable in: - Oracle - Postgres Bug: T188741 Change-Id: Ibe1cc363d21fb96f38c263181bf30a429a1c7b45
2018-03-12 16:21:02 +00:00
[ 'modifyField', 'revision', 'rev_text_id', 'patch-rev_text_id-default.sql' ],
Overhaul site_stats table The site stats table holds a bunch of metric fields, two of which are of data type "bigint unsigned", 3 are "bigint" (signed) and one is int (signed). Also the default values differ widely: It is 0 on the "unsigned" fields and the "int" field, but -1 on the three others. This patch makes all of this more consistent: Set all fields (except the ss_row_id, which isn't changed) data type to "bigint unsigned". Also set NULL as the default value for all those fields. Obviously -1 isn't a possible default value any more. Also, 0 can easily be mistaken for a real value (e.g. ss_active_users=0 --> "there is nobody active on this wiki"). NULL, by it's definition, is the value of choice for a value to insert into fields of which we don't know a correct value. The respective patch files were tested locally against MySql, Sqlite, Postgres and SQL Server 2016. Neither oracle nor the upgrade with update.php was tested. Bug: T56888 Change-Id: I7d42aae434852a56b6f8dd559d8a5f3bce416021
2017-05-08 19:31:54 +00:00
[ 'modifyTable', 'site_stats', 'patch-site_stats-modify.sql' ],
Populate ar_rev_id and make it non-nullable Revisions deleted before MediaWiki 1.5 do not have a value in this field. This is going to be a problem for migration to the MCR schema, so provide a maintenance script to clean this up. Then, for good measure, change the schema to make the field non-nullable. Bug: T182678 Change-Id: Ie2e11f12a30f379db32c3e074658012c6f93adb0
2018-01-04 19:35:13 +00:00
[ 'populateArchiveRevId' ],
Change index on rc_namespace, rc_title to rc_namespace, rc_title, rc_timestamp Bug: T190444 Change-Id: I5c59f1ee9306710505654a8db965f85ebf855873
2018-03-22 19:46:49 +00:00
[ 'addIndex', 'recentchanges', 'rc_namespace_title_timestamp',
'patch-recentchanges-nttindex.sql' ],
Introduce change_tag_def table Table defining tag names for IDs. Also stores hit counts to avoid expensive queries on change_tag See T185355 for more information Bug: T193867 Bug: T185355 Change-Id: I4fd943589b3ed304471304c8beda15327a8edbcf
2018-05-04 17:29:53 +00:00
// 1.32
[ 'addTable', 'change_tag_def', 'patch-change_tag_def.sql' ],
Populate externallinks.el_index_60 and drop default Adds a maintenance script to populate the field, has that be automatically run during update.php, and drops the no-longer-needed default value on the column (where possible: mssql has some sort of constraint thing going on that I have no idea how it works). Bug: T59176 Change-Id: I971edf013a1a39466aca3b6e34c915cb24fd3aa7
2016-11-18 20:42:11 +00:00
[ 'populateExternallinksIndex60' ],
[ 'modifyfield', 'externallinks', 'el_index_60',
'patch-externallinks-el_index_60-drop-default.sql' ],
Deduplicate archive.ar_rev_id Old bugs and such may have left the archive table with multiple rows using the same ar_rev_id, or rows that also exist in the revision table. These need to be cleaned up for MCR. The maintenance script added here will delete rows that appear to be duplicates of the same change, and will assign new IDs to rows that do not appear to be duplicates. Bug: T193180 Change-Id: I39b0825c9469e074ded3df33a4f06a1ef0edb494
2018-04-27 17:10:36 +00:00
[ 'runMaintenance', DeduplicateArchiveRevId::class, 'maintenance/deduplicateArchiveRevId.php' ],
Add ct_tag_id field to change_tag table Part of normalizing the table Bug: T193867 Change-Id: I8c38e673aab14c5b87e5501da1a752c5bd4709c8
2018-05-11 19:16:37 +00:00
[ 'addField', 'change_tag', 'ct_tag_id', 'patch-change_tag-tag_id.sql' ],
Make archive.ar_rev_id unique To follow up I39b0825c, this change replaces the existing non-unique index on the column with a unique index, to help avoid some of these sort of bugs in the future. Bug: T193180 Change-Id: I932478c9c6a13210bc9dff75286d0f08da56682c
2018-04-27 17:11:01 +00:00
[ 'addIndex', 'archive', 'ar_revid_uniq', 'patch-archive-ar_rev_id-unique.sql' ],
Run populateContentTables.php from update.php Since update.php will eventually be dropping the old columns and fields, we should make sure the migration script gets run first. Bug: T197818 Change-Id: I47f5ba4e21b4fe2ef0beb9fc83896cd4b0a0d505
2018-07-10 17:09:37 +00:00
[ 'populateContentTables' ],
Rename index type_action to log_type_action Bug: T51199 Change-Id: I697fd5689e573bfa965ca75385f919c9a8403c14
2018-07-11 14:36:27 +00:00
[ 'addIndex', 'logging', 'log_type_action', 'patch-logging-log-type-action-index.sql' ],
[ 'dropIndex', 'logging', 'type_action', 'patch-logging-drop-type-action-index.sql' ],
Convert numerous UNIQUE INDEX to PRIMARY KEY MySQL, SQLite, PostgreSQL and MSSQL done with transitional patches. One additional duplicate index removed from PostgreSQL schema. Having a PK is essential to do maintenance, specially on large tasks. By not having a PK it is impossible to add it in a safe way if not done directly on the master. Having a PK means that we can easily change the PK into another one if needed in the future. The ones we chose might not be the best ones, but will allow us to get them changed. Bug: T198811 Change-Id: I6b96a427687085c6c24bcd759c9739f81288b919
2018-07-04 19:13:07 +00:00
[ 'renameIndex', 'interwiki', 'iw_prefix', 'PRIMARY', false, 'patch-interwiki-fix-pk.sql' ],
[ 'renameIndex', 'page_props', 'pp_page_propname', 'PRIMARY', false,
'patch-page_props-fix-pk.sql' ],
[ 'renameIndex', 'protected_titles', 'pt_namespace_title', 'PRIMARY', false,
'patch-protected_titles-fix-pk.sql' ],
[ 'renameIndex', 'site_identifiers', 'site_ids_type', 'PRIMARY', false,
'patch-site_identifiers-fix-pk.sql' ],
Add index on rc_this_oldid Approved by TechComm Bug: T139012 Change-Id: I0ccfd26d68a5ceef552ae3aa37a6e345b24ff84e
2018-08-02 19:12:07 +00:00
[ 'addIndex', 'recentchanges', 'rc_this_oldid', 'patch-recentchanges-rc_this_oldid-index.sql' ],
Drop the transcache table from the schema Bug: T189702 Change-Id: I3286a99165953392126fcff07d565738863de6a1
2018-08-28 17:44:03 +00:00
[ 'dropTable', 'transcache' ],
Schema change for reading ct_tag_id instead of ct_tag Adding unique index on ct_tag_id and making indexes on ct_tag non unique Bug: T193874 Change-Id: I24609c57e47308d1330a97527f4ea374d0d307ba
2018-08-28 21:32:55 +00:00
[ 'runMaintenance', PopulateChangeTagDef::class, 'maintenance/populateChangeTagDef.php' ],
[ 'addIndex', 'change_tag', 'change_tag_rc_tag_id',
'patch-change_tag-change_tag_rc_tag_id.sql' ],
Make Schema changes for Partial Blocks Update the database schema so a block can be switched between a sitewide and partial block. Also add the restrictions table for specifiying the partial blocks. Bug: T197144 Change-Id: I4a725312c4b980a1b14e5ca826069fa2278a5913
2018-06-18 14:26:20 +00:00
[ 'addField', 'ipblocks', 'ipb_sitewide', 'patch-ipb_sitewide.sql' ],
[ 'addTable', 'ipblocks_restrictions', 'patch-ipblocks_restrictions-table.sql' ],
Migrate image descriptions from image_comment_temp image_comment_temp was always intended to be temporary, until an expensive schema change on Wikimedia Commons's image table could be done. Now that that has been done, stop writing image_comment_temp and add a migration script to copy existing data into img_description_id. Ic8efeddc will remove the reads from image_comment_temp and drop the image_comment_temp table. Bug: T188132 Change-Id: Iab5f521577a415b2dc213b517ee8a0dca4fdd0aa
2018-03-07 16:40:56 +00:00
[ 'migrateImageCommentTemp' ],
Drop ct_tag column from change_tag table Bug: T194163 Change-Id: I05d43510b51a67733b0107f0a768e261fe8ddabd
2018-11-14 20:20:11 +00:00
// 1.33
[ 'dropField', 'change_tag', 'ct_tag', 'patch-drop-ct_tag.sql' ],
Drop tag_summary and valid_tag tables Bug: T209525 Change-Id: I153607239145a772f5ea47eefd3340096a494b4b
2018-12-12 19:20:42 +00:00
[ 'dropTable', 'valid_tag' ],
[ 'dropTable', 'tag_summary' ],
Mostly drop old comment schemas This removes most of the pre-CommentStore text columns, and the $wgCommentTableSchemaMigrationStage setting that used to determine whether the columns were used. rev_comment remains in the code, as on Wikimedia wikis the revision table is too large to alter at this time. A future change will combine that with the removal of rev_user_text, rev_content_model, and rev_content_format (and the addition of rev_comment_id and rev_actor). CommentStore's constructor continues to take a $stage parameter, and continues to have the logic for handling it, for the benefit of extensions that might need their own migration process. Bug: T166733 Change-Id: I1479c73774e01ead1490adf6128f820c09bce9d4
2019-01-04 18:55:11 +00:00
[ 'dropField', 'archive', 'ar_comment', 'patch-archive-drop-ar_comment.sql' ],
[ 'dropField', 'ipblocks', 'ipb_reason', 'patch-ipblocks-drop-ipb_reason.sql' ],
[ 'dropField', 'image', 'img_description', 'patch-image-drop-img_description.sql' ],
[ 'dropField', 'oldimage', 'oi_description', 'patch-oldimage-drop-oi_description.sql' ],
[ 'dropField', 'filearchive', 'fa_description', 'patch-filearchive-drop-fa_description.sql' ],
[ 'dropField', 'recentchanges', 'rc_comment', 'patch-recentchanges-drop-rc_comment.sql' ],
[ 'dropField', 'logging', 'log_comment', 'patch-logging-drop-log_comment.sql' ],
[ 'dropField', 'protected_titles', 'pt_reason', 'patch-protected_titles-drop-pt_reason.sql' ],
Mostly drop old pre-actor user schemas This removes most of the pre-actor user and user_text columns, and the $wgActorTableSchemaMigrationStage setting that used to determine whether the columns were used. rev_user and rev_user_text remain in the code, as on Wikimedia wikis the revision table is too large to alter at this time. A future change will combine that with the removal of rev_comment, rev_content_model, and rev_content_format (and the addition of rev_comment_id and rev_actor). ActorMigration's constructor continues to take a $stage parameter, and continues to have the logic for handling it, for the benefit of extensions that might need their own migration process. Code using ActorMigration for accessing the core fields should be updated to use the new actor fields directly. That will be done for in a followup. Bug: T188327 Change-Id: Id35544b879af1cd708f3efd303fce8d9a1b9eb02
2019-07-23 17:40:52 +00:00
// 1.34
[ 'dropField', 'archive', 'ar_user', 'patch-archive-drop-ar_user.sql' ],
[ 'dropField', 'ipblocks', 'ipb_by', 'patch-ipblocks-drop-ipb_by.sql' ],
[ 'dropField', 'image', 'img_user', 'patch-image-drop-img_user.sql' ],
[ 'dropField', 'oldimage', 'oi_user', 'patch-oldimage-drop-oi_user.sql' ],
[ 'dropField', 'filearchive', 'fa_user', 'patch-filearchive-drop-fa_user.sql' ],
[ 'dropField', 'recentchanges', 'rc_user', 'patch-recentchanges-drop-rc_user.sql' ],
[ 'dropField', 'logging', 'log_user', 'patch-logging-drop-log_user.sql' ],
Create new table for watchlist expiry This table will store expiries for watchlist items, so that pages can be automatically unwatched at a specific time. Bug: T240094 Change-Id: I014ffccb91969e7a222a83858c55e71067b0f2af
2020-02-07 19:15:46 +00:00
// 1.35
[ 'addTable', 'watchlist_expiry', 'patch-watchlist_expiry.sql' ],
Drop DEFAULT from *_actor columns for SQLite tables that still have it These were left out by mistake (made easier by a bug where some phpunit tests never run). Fixing the test bug is blocked on fixing the SQLite schema so that DatabaseSqliteTest.php passes when it actually runs. Bug: T246077 Change-Id: I75d7a7fb56a07c2984e987b6136e1fd00615c421
2020-03-20 03:53:52 +00:00
[ 'modifyfield', 'filearchive', 'fa_actor', 'patch-filearchive-drop-fa_actor-DEFAULT.sql' ],
[ 'modifyfield', 'recentchanges', 'rc_actor', 'patch-recentchanges-drop-rc_actor-DEFAULT.sql' ],
Add schema change to make page.page_restrictions column nullable The page.page_restrictions field was used to store protection settings for pages before MediaWiki 1.10 introduced the page_restrictions table. update.php has since been running the updateRestrictions.php maintenance script to migrate data from the legacy field to the new table. In preparation for dropping this field, it is necessary to first make this column nullable, so that we can remove code that references it during write operations. This patch adds migrations for MySQL and SQLite to make the column type 'tinyblob NULL'. Postgres does not seem to require a schema change, as the field definition there is 'TEXT' rather than 'TEXT NOT NULL'. Bug: T218446 Change-Id: I626859cdb5ab81c504a986129d21059ab088b8bd
2020-03-18 23:33:48 +00:00
[ 'modifyfield', 'logging', 'log_actor', 'patch-logging-drop-log_actor-DEFAULT.sql' ],
[ 'modifyField', 'page', 'page_restrictions', 'patch-page_restrictions-null.sql' ],
Rename ipb_address to ipb_address_unique This is how it's named in WMF production and the Postgres. Converging names would help us to keep everything consistent, for example if we need to force this index in the code. For changing this index in Sqlite, we don't need to make a temp table as this only touches the index and not the table structure. Bug: T250071 Change-Id: I0838753b809680af3ee06d9c4f6d21d95b8982cc
2020-04-21 21:51:33 +00:00
[ 'renameIndex', 'ipblocks', 'ipb_address', 'ipb_address_unique', false,
'patch-ipblocks-rename-ipb_address.sql' ],
Alter `revision` for actor, comment, and MCR We're finally to the point of making the massive alter to the `revision` table that we've been building up to for 2.5 years now. Changes here are: * Drop `rev_text_id`, `rev_content_model`, and `rev_content_format` that MCR obsoleted. * Drop `ar_text_id`, `ar_content_model`, and `ar_content_format` that MCR obsoleted. * Replace `rev_comment` with `rev_comment_id`. * Replace `rev_user` and `rev_user_text` with `rev_actor`, plus associated index changes. Future patches will make the code changes to migrate data from `revision_actor_temp` and `revision_comment_temp` into the new `revision` columns. Bug: T251343 Bug: T184615 Bug: T215466 Change-Id: I18071a2fe45907a0cf1b0fefebd96a97a2dacb7b
2019-11-21 20:47:13 +00:00
[ 'addField', 'revision', 'rev_actor', 'patch-revision-actor-comment-MCR.sql' ],
[ 'dropField', 'archive', 'ar_text_id', 'patch-archive-MCR.sql' ],
Remove ipb_anon_only from ipb_address_unique UNIQUE INDEX Bug: T251188 Change-Id: I4618f659be64134664ac1644de2b51d74f000e4c
2020-05-04 20:16:03 +00:00
[ 'doFixIpbAddressUniqueIndex' ],
Migrate content table to abstract schema content.content_id was BIGINT in MySQL (and Sqlite) but INT in Postgres so making Postgres BIGINT as well. Bug: T230428 Bug: T164898 Change-Id: Ib8492e224478dc069ba17e489f7b2bb22d5da804
2020-07-20 00:30:37 +00:00
[ 'modifyField', 'actor', 'actor_name', 'patch-actor-actor_name-varbinary.sql' ],
Add 1.36 Database Updater sections for MySQL/SQLite I presume we're not backporting these... Change-Id: Id6a00faa440d34e5ba7812b8959367b745fd111b
2020-08-25 15:29:14 +00:00
// 1.36
Migrate content table to abstract schema content.content_id was BIGINT in MySQL (and Sqlite) but INT in Postgres so making Postgres BIGINT as well. Bug: T230428 Bug: T164898 Change-Id: Ib8492e224478dc069ba17e489f7b2bb22d5da804
2020-07-20 00:30:37 +00:00
[ 'modifyField', 'content', 'content_id', 'patch-content-content_id-fix_not_null.sql' ],
Migrate redirect table to abstract schema Changing "varchar() binary" to varbinary in MySQL and Sqlite for two columns: rd_title and rd_fragment. Fixing db drifts of schema in Postgres: - Setting the data type of rd_namespace from SMALLINT and setting its default - Set empty string as default of rd_title - Changing datatype of rd_interwiki to varchar (PG supports that) Bug: T164898 Bug: T230428 Change-Id: I9563792b1fc0ce5f3de78c08703a768a0c2e99d0
2020-08-09 19:05:37 +00:00
[ 'modifyField', 'redirect', 'rd_title', 'patch-redirect-rd_title-varbinary.sql' ],
Migrate pagelinks table to abstract schema In order to migrate MySQL and Sqlite to abstract schema changed the pl_title data type from varchar binary to varbinary. This wouldn't affect production. For migrating Postgres: - Dropping foreign key on pl_from - Changing data type of pl_namespace from SMALLINT to INT and setting its default - Setting default of empty string for pl_title - Completely rewriting indexes to make it synced with MySQL Bug: T164898 Bug: T230428 Change-Id: I4af8202742a1826e6b3f8ff36cf4f7b612b82690
2020-08-15 19:01:57 +00:00
[ 'modifyField', 'pagelinks', 'pl_title', 'patch-pagelinks-pl_title-varbinary.sql' ],
Migrate templatelinks table to abstract schema In order to migrate MySQL and Sqlite to abstract schema changed the tl_title data type from varchar binary to varbinary. This wouldn't affect production. For migrating Postgres: - Dropping foreign key on tl_from - Changing data type of tl_namespace from SMALLINT to INT and setting its default - Setting default of empty string for tl_title - Completely rewriting indexes to make it synced with MySQL Bug: T164898 Bug: T230428 Change-Id: Idbb65d870f58f7146b9c8bd860e6530bef1e0f12
2020-08-22 12:57:42 +00:00
[ 'modifyField', 'templatelinks', 'tl_title', 'patch-templatelinks-tl_title-varbinary.sql' ],
Migrate imagelinks table to abstract schema In order to migrate MySQL and Sqlite to abstract schema changed the il_to data type from varchar binary to varbinary. This wouldn't affect production. For migrating Postgres: - Dropping foreign key on il_from - Setting default of empty string for il_to - Completely rewriting indexes to make it synced with MySQL Bug: T164898 Bug: T230428 Change-Id: I59f0d0a56d938a168bf1c7de2a1be47f15d1add1
2020-08-22 20:51:25 +00:00
[ 'modifyField', 'imagelinks', 'il_to', 'patch-imagelinks-il_to-varbinary.sql' ],
Migrate langlinks to abstract schema In order to migrate MySQL and Sqlite to abstract schema changed the ll_title data type from varchar binary to varbinary. This wouldn't affect production. For migrating Postgres: - Dropping foreign key on ll_from - Setting default of empty string for ll_lang and ll_title - Make ll_lang and ll_title both non-nullable to be in sync with MySQL - Turning the unique index to primary key, similar to MySQL - Renaming an index to sync with MySQL Bug: T164898 Bug: T230428 Change-Id: I57f22896ff67266f99bf08f6dd1b9cc4c51b1db9
2020-08-29 17:00:04 +00:00
[ 'modifyField', 'langlinks', 'll_title', 'patch-langlinks-ll_title-varbinary.sql' ],
Migrate iwlinks to abstract schema In order to migrate MySQL and Sqlite to abstract schema changed the iwl_title data type from varchar binary to varbinary. This wouldn't affect production. For migrating Postgres: - Turning the unique index to PK to make it in sync with MySQL Bug: T164898 Bug: T230428 Change-Id: Iaa625b66c874023b8cf2403917fa2fa120279208
2020-08-29 17:25:15 +00:00
[ 'modifyField', 'iwlinks', 'iwl_title', 'patch-iwlinks-iwl_title-varbinary.sql' ],
Migrate category to abstract schema In order to migrate MySQL and Sqlite to abstract schema changed the cat_title data type from varchar binary to varbinary. This wouldn't affect production. For migrating Postgres, renamed two indexes from category_* to cat_* to make it in sync with MySQL/Sqlite Bug: T164898 Bug: T230428 Change-Id: Iad11aa4f7d809465cb20ac9748bf52b0e1bcd5a4
2020-09-05 18:33:21 +00:00
[ 'modifyField', 'category', 'cat_title', 'patch-category-cat_title-varbinary.sql' ],
Migrate querycache to abstract schema Turning qc_title to varbinary in MySQL to make it consistent with the rest of fields. For Postgres: - Setting 0 as default for qc_value and qc_namespace - Changing data type of qc_namespace from SMALLINT to INT to make it the same with MySQL/Sqlite - Renaming index to make it the same with other schemas - Setting empty string as default of qc_title Bug: T230428 Bug: T164898 Change-Id: I81527121609014d29182ae735a2c1f532d7d4d2a
2020-09-26 13:39:59 +00:00
[ 'modifyField', 'querycache', 'qc_title', 'patch-querycache-qc_title-varbinary.sql' ],
Migrate querycachetwo table to abstract schema Yes, name of that table is really querycachetwo. For migrating MySQL/Sqlite, changed data type of qcc_title and qcc_titletwo to varbinary. For migrating Postgres, just renaming indexes to stay in sync with MySQL/Sqlite was enough. Bug: T230428 Change-Id: I43952836ce184419622a6f851cb5e9319172d656
2020-09-26 14:39:53 +00:00
[ 'modifyField', 'querycachetwo', 'qcc_title', 'patch-querycachetwo-qcc_title-varbinary.sql' ],
Migrate watchlist table to Abstract schema Postgres: - Set empty string as default for wl_title to match MySQL - Drop foreign key from wl_user - Change wl_namespace datatype from SMALLINT to INT to match MySQL/SQLite - Drop PG-specific indexes and sync them with MySQL Bug: T230428 Bug: T164898 Change-Id: Ie996b81ca59069443976b90d7bcdce29997d768a
2020-10-18 09:43:04 +00:00
[ 'modifyField', 'watchlist', 'wl_title', 'patch-watchlist-wl_title-varbinary.sql' ],
Migrate protected_titles to abstract schema For Postgres: - Drop foreign key from pt_title - Change pt_user to non-nullable to sync with MySQL - Change pt_expiry to non-nullable to sync with MySQL - Modify pt_reason_id to use BIGINT to sync with MySQL - Drop default from pt_create_perm field since MySQL and SQLite don't have it and the field is not nullable. - For MySQL/SQLite: - Modify pt_title to use varbinary - Drop DEFAULT constraint from pt_expiry (Postgres already does not have it) Bug: T230428 Bug: T164898 Change-Id: Iff193754260046222ba9b7e704c46e27f21b1a6b
2020-10-27 05:55:50 +00:00
[ 'modifyField', 'protected_titles', 'pt_title', 'patch-protected_titles-pt_title-varbinary.sql' ],
[ 'modifyField', 'protected_titles', 'pt_expiry', 'patch-protected_titles-pt_expiry-drop-default.sql' ],
Migrate revision_actor_temp to abstract schema For Postgres: - Drop foreign key from 'revactor_page' - Change datatype of 'revactor_actor' to BigInt as in MySQL/SQLite - Make 'revactor_page' non-nullable as in MySQL/SQLite For MySQL/SQLite: - Drop empty string default constraint from 'revactor_timestamp' as this is not allowed in the corresponding PG's TIMESTAMPTZ field Bug: T230428 Bug: T164898 Change-Id: I8c5c4b338a3000b1e4c2ab82fdae4a9819925868
2020-11-10 07:48:11 +00:00
[ 'modifyField', 'ip_changes', 'ipc_rev_timestamp', 'patch-ip_changes-pc_rev_timestamp-drop-default.sql' ],
[ 'modifyField', 'revision_actor_temp', 'revactor_timestamp', 'patch-revactor_timestamp-drop-default.sql' ],
Rename namespace_title index on watchlist to wl_namespace_title Indexes need to have prefixes, to avoid clashes in several RDBMSes where indexes are global Bug: T266228 Change-Id: I96a04903f6123d1fb8081fcf15cdd1f29708d320
2020-11-16 14:24:24 +00:00
[ 'renameIndex', 'watchlist', 'namespace_title', 'wl_namespace_title', false,
'patch-watchlist-namespace_title-rename-index.sql' ],
Migrate job to abstract schema Postgres: - Drop deafault from job_id - Add default to job_cmd - Change job_namespace datatype to INTEGER - Drop job_cmd_namespace_title index - Add job_cmd index on the same fields as MySQL - Rename index job_timestamp_idx MySQL: - Change job_title datatype to VARBINARY - Change job_timestamp datatype to BINARY (mwtimestamp) - Change job_token_timestamp datatype to BINARY (mwtimestamp) Bug: T230428 Bug: T164898 Bug: T42626 Change-Id: I207aefc48c7bcbb5b5362af4b63d9a1383019a6d
2020-11-18 05:50:39 +00:00
[ 'modifyField', 'job', 'job_title', 'patch-job-job_title-varbinary.sql' ],
Migrate slot_roles and content_models to abstract schema These tables don't have drift between MySQL and Postgres but their primary keys don't have explicit "NOT NULL" statement making them nullable in sqlite. Fixing this drift. Also changing the PK fields of these two tables from smallint to int, given that PG would be complicated with smallint auto_increment PKs Bug: T230428 Bug: T258366 Change-Id: Icf6ce044eaf0f09b1a2bdd8a1f618cef1e0415bf
2020-08-09 15:45:51 +00:00
[ 'modifyField', 'slot_roles', 'role_id', 'patch-slot_roles-role_id-fix_not_null.sql' ],
[ 'modifyField', 'content_models', 'model_id', 'patch-content_models-model_id-fix_not_null.sql' ],
Migrate categorylinks to abstract schema To get MySQL/SQLite migrated, changing type of cl_to and cl_sortkey_prefix from "varchar() binary" to varbinary For Postgres: - Dropping foreign key on cl_from - Setting proper default for cl_from, cl_to, cl_sortkey, cl_collation - Set cl_sortkey to not nullable - Dropping unique index cl_from which in turn should become PK - Adding several missing indexes - Fixing columns of cl_sortkey Bug: T230428 Bug: T164898 Change-Id: I83043ef41f9c753734f1e4b51237d979031dd71a
2020-11-28 11:16:20 +00:00
[ 'modifyField', 'categorylinks', 'cl_to', 'patch-categorylinks-cl_to-varbinary.sql' ],
Migrate logging to abstract schema Some changes needed for the migration: Postgres: - Add default to five fields that have it in MySQL - Make log_params not nullable - Change log_comment_id and log_actor type to big integer - Change log_namespace to integer - Drop logging_actor_time index MySQL/SQLite - Change log_title to varbinary/BLOB Bug: T230428 Bug: T164898 Change-Id: Iad59d2a78f61d93637917ca320d3e173863ce5e1
2020-12-06 00:12:01 +00:00
[ 'modifyField', 'logging', 'log_title', 'patch-logging-log_title-varbinary.sql' ],
Rename user_properties index Use uniform prefix with the column names Bug: T270033 Change-Id: I9ee1f8ac9a8d0e575e16344910495f341c2714db
2020-12-14 16:37:53 +00:00
[ 'renameIndex', 'user_properties', 'user_properties_property', 'up_property', false,
'patch-user_properties-rename-index.sql' ],
Rename all sites indexes Use uniform prefix with the column names Bug: T270033 Change-Id: I771ffc67a1363d8877c57dce1d8b2acdca8fe5bb
2020-12-15 04:16:54 +00:00
[ 'renameIndex', 'sites', 'sites_global_key', 'site_global_key', false, 'patch-sites-rename-indexes.sql' ],
Rename four logging indexes to have log_ prefix To follow database coding convention and avoid clashes in RDBMS engines where indexes are global Bug: T270033 Change-Id: I17028bba489d04b01d22c39dc8935a4f0f771c7e
2020-12-13 01:52:49 +00:00
[ 'renameIndex', 'logging', 'type_time', 'log_type_time', false, 'patch-logging-rename-indexes.sql' ],
Migrate filearchive to abstract schema For MySQL: - Drop default from fa_deleted_timestamp and fa_timestamp - Change fa_name and fa_storage_group from varchar() binary to varbinary() For Postgres: - Set default for three fields - Drop foreign key on fa_deleted_user - Change field type for five fields - Rename indexes to make it make in sync with MySQL/Postgres - Rebuild an index to make it in sync MySQL/Postgres Bug: T230428 Bug: T164898 Bug: T42626 Change-Id: Ia2be151c46c73f15592db03540834a6456460cac
2020-12-20 21:42:14 +00:00
[ 'modifyField', 'filearchive', 'fa_name', 'patch-filearchive-fa_name.sql' ],
Migrate oldimage to abstract schema For MySQL/Sqlite: - Changing oi_name and oi_archive_name to varbinary instead of "varchar binary" - Dropping default from oi_timestamp For Postgres: - Adding the correct default to seven fields - Removing incorrect default from oi_metadata - Add missing index oi_actor_timestamp - Change four fields to have correct data type - Make oi_major_mime and oi_minor_mime not nullable - Drop foreign key on oi_name Bug: T230428 Bug: T164898 Change-Id: I4dff0e48081a5797a29513f9c8b87f9ffcaadb5d
2021-01-16 19:42:23 +00:00
[ 'modifyField', 'oldimage', 'oi_name', 'patch-oldimage-oi_name-varbinary.sql' ],
Migrate objectcache to abstract schema For Postgres: - Drop Unique constraint on `keyname` and make primary key - Change type of `value` from BYTEA to TEXT and drop its default - Make `value` nullable to sync with MySQL/SQLite MySQL: - Change exptime from DATETIME to TIMESTAMP MySQL/SQLite: - Make 'exptime' not nullable Bug: T230428 Bug: T164898 Change-Id: Iab9de8a1bb2cb01b6e3e69e66f1bbe089d53d0a7
2020-10-23 13:11:39 +00:00
[ 'modifyField', 'objectcache', 'exptime', 'patch-objectcache-exptime-notnull.sql' ],
Migrate ipblocks to abstract schema For MySQL/Sqlite: - Drop default values of ipb_timestamp and ipb_expiry as part of standardizing timestamp columns For Postgres: - Drop foreign key on two columns as approved by the RFC - Set default of ipb_user - Make three columns not nullable to sync with MySQL - Change data type of two columns to BIGINT to be the same as MySQL Bug: T230428 Bug: T164898 Bug: T42626 Change-Id: I2c5303d76c6ce059d7fef324a4521c6336c5b1f3
2021-01-23 05:02:25 +00:00
[ 'modifyField', 'ipblocks', 'ipb_timestamp', 'patch-ipblocks-ipb_timestamp-drop-default.sql' ],
Standardize archive indexes For Sqlite and MySQL, renaming name_title_timestamp to ar_name_title_timestamp so it follows the database convention. For Postgres: - Rename archive_name_title_timestamp to ar_name_title_timestamp - Drop archive_actor (that has only ar_actor) - Add ar_actor_timestamp (that has ar_actor, ar_timestamp) This fixes drifts of PG and MySQL and makes work for abstracting the table easier. Bug: T230428 Bug: T164898 Change-Id: I123a4c47602bdd415f0fe5823f96159dcd0d84b8
2021-01-23 09:00:00 +00:00
[ 'renameIndex', 'archive', 'name_title_timestamp', 'ar_name_title_timestamp', false,
'patch-archive-rename-name_title_timestamp-index.sql' ],
Migrate image table to abstract schema For MySQL/Sqlite: - Change datatype of img_name from "varchar() binary" to varbinary. - Drop default of img_timestamp For Postgres: - Adding two missing indexes. - Renaming two indexes - Setting default value for five fields - Fix data type of four fields - Drop default of img_metadata - Make three fields not nullable Bug: T230428 Bug: T164898 Change-Id: I237af3558b0e1c1fecd874c3c90ba6780e50aaa4
2021-01-28 19:13:03 +00:00
[ 'modifyField', 'image', 'img_name', 'patch-image-img_name-varbinary.sql' ],
Rename site_identifiers indexes to have si_ prefix Bug: T270033 Change-Id: I6751f0fd992054b61222ece55c83d05d24af9000
2020-12-21 12:52:44 +00:00
[ 'renameIndex', 'site_identifiers', 'site_ids_key', 'si_key', false,
'patch-site_identifiers-rename-indexes.sql' ],
Migrate recentchanges table to abstract schema This table is massive but thankfully we fixed most of its complexities in previous patches. For MySQL/Sqlite: - Change type of rc_title and rc_source from "varchar binary" to "varbinary" - Drop default of rc_timestamp - Change rc_timestamp from varbinary(14) to binary(14) to standardize timestamp datatypes One index doesn't follow the uniform prefix rule but since it's in a maintenance script, will fix that in a follow up. Bug: T230428 Bug: T42626 Change-Id: I13994e02ad3a2293148346ef7be96746578ad854
2021-02-26 12:52:22 +00:00
[ 'modifyField', 'recentchanges', 'rc_title', 'patch-recentchanges-rc_title-varbinary.sql' ],
Rename new_name_timestamp on recentchanges to rc_new_name_timestamp To make it have a uniform prefix for index and column names Bug: T270033 Change-Id: I8eb600416913092bd5aeb70389bba6e8a54d1d57
2021-02-27 18:37:49 +00:00
[ 'renameIndex', 'recentchanges', 'new_name_timestamp', 'rc_new_name_timestamp', false,
'patch-recentchanges-rc_new_name_timestamp.sql' ],
Migrate archive table to abstract schema One of the last ones left. For MySQL/Sqlite: - Dropping default of ar_timestamp, empty string is not a valid timestamp. - Changing ar_title from "varchar() binary" to varbinary for Postgres: - Set default for ar_namespace and ar_title - Change datatype of ar_comment_id, ar_actor, ar_namespace The indexes were fixed separately. Bug: T230428 Bug: T164898 Bug: T42626 Depends-On: I83cf1cd51ac9cf933c9175cefd6e38a6914f3494 Change-Id: Ic1d13a82b27f7fa39a0f0ea9c5b7b193b007e4ab
2021-03-13 19:49:25 +00:00
[ 'modifyField', 'archive', 'ar_title', 'patch-archive-ar_title-varbinary.sql' ],
Migrate page to abstract schema Postgres: - Change page_namespace from smallint to int - Change page_random from numeric with arbitrary precision to float - Make page_touched not nullable MySQL/SQLite: - Change datatype of page_title from varchar (with binary collation) to varbinary(255) - Drop default empty string from timestamp field of page_touched Bug: T230428 Bug: T164898 Change-Id: Ibdaf332ea1da309d31d35a6ebbc1b8fefced335e
2020-11-23 04:33:36 +00:00
[ 'modifyField', 'page', 'page_title', 'patch-page-page_title-varbinary.sql' ],
Prepare for migrating `user` to abstract schema Split off to make the migration patch smaller Postgres: - Make user_touched not nullable MySQL/SQlite - Change user_name from varchar to varbinary - Change user_name from varchar to varbinary - Drop empty string default from user_touched (Timestamp field) Bug: T230428 Bug: T164898 Change-Id: I8fe0b1fb2af3149a2e2fdae7bb056ac6f863b09c
2021-03-27 09:28:18 +00:00
[ 'modifyField', 'user', 'user_name', 'patch-user_table-updates.sql' ],
Migrate page to abstract schema Postgres: - Change page_namespace from smallint to int - Change page_random from numeric with arbitrary precision to float - Make page_touched not nullable MySQL/SQLite: - Change datatype of page_title from varchar (with binary collation) to varbinary(255) - Drop default empty string from timestamp field of page_touched Bug: T230428 Bug: T164898 Change-Id: Ibdaf332ea1da309d31d35a6ebbc1b8fefced335e
2020-11-23 04:33:36 +00:00
Rename `page_timestamp` revision index Rename to `rev_page_timestamp` Bug: T270033 Depends-On: I16fc273b14e7f4b00e8c31ec1ed7712149aafe37 Change-Id: I93fcfb3caf8c6bd7f9e46921065b751c23571ae1
2021-03-22 14:42:19 +00:00
// 1.37
[ 'renameIndex', 'revision', 'page_timestamp', 'rev_page_timestamp', false,
'patch-revision-rename-index.sql' ],
objectcache: add last-modified token field to objectcache table Also added token and flags fields. The token field can be used as a tie-breaker for modtime and also for faster cas() operations. The flags field makes serialization and compression format changes easier in the future. Bug: T274174 Change-Id: I45731a877b21835652993c2d285165a76eeae3e9
2021-02-24 15:44:24 +00:00
[ 'addField', 'objectcache', 'modtoken', 'patch-objectcache-modtoken.sql' ],
Migrate revision table to abstract schema Postgres: - Drop foreign key from rev_page - Make rev_page not nullable - Change rev_comment_id from int to bigint - Change rev_actor from int to bigint - Sync rev_page_id index with MySQL MySQL/SQlite: - Drop default from rev_timestamp Additional changes in the generator script to handle more formatting issues due to use of additional custom table options Bug: T230428 Bug: T164898 Change-Id: Ia07dd52e43123473a1728523a3f863280537db8e
2021-03-21 15:32:35 +00:00
[ 'modifyField', 'revision', 'rev_timestamp', 'patch-revision-rev_timestamp-drop-default.sql' ],
Add index on oldimage.oi_timestamp Mirroring what happens on image table. Bug: T279982 Change-Id: Ib67c32b10d3b88e09514d8fbb5dcb4f977108ba2
2021-04-24 10:42:10 +00:00
[ 'addIndex', 'oldimage', 'oi_timestamp', 'patch-oldimage-oi_timestamp.sql' ],
Convert all array() syntax to [] Per wikitech-l consensus: https://lists.wikimedia.org/pipermail/wikitech-l/2016-February/084821.html Notes: * Disabled CallTimePassByReference due to false positives (T127163) Change-Id: I2c8ce713ce6600a0bb7bf67537c87044c7a45c4b
2016-02-17 09:09:32 +00:00
];
* Split Mysql/Sqlite updates into their own files * Rename Update -> DatabaseUpdaters to be more consistent with DatabaseInstaller * Made DatabaseUpdaters abstract and merged the Updaters interface in, had Mysql/Oracle/Sqlite subclass it. Entry point is now factory DatabaseUpdaters::newForDB()
2010-07-20 22:28:50 +00:00
}
Moved SQLite specific functions to SqliteUpdater
2010-09-11 09:49:57 +00:00
Remove ipb_anon_only from ipb_address_unique UNIQUE INDEX Bug: T251188 Change-Id: I4618f659be64134664ac1644de2b51d74f000e4c
2020-05-04 20:16:03 +00:00
/**
* Check whether an index contain a field
*
* @param string $table Table name
* @param string $index Index name to check
* @param string $field Field that should be in the index
* @return bool
*/
protected function indexHasField( $table, $index, $field ) {
$info = $this->db->indexInfo( $table, $index, __METHOD__ );
if ( $info ) {
foreach ( $info as $column ) {
if ( $column == $field ) {
$this->output( "...index $index on table $table includes field $field.\n" );
return true;
}
}
}
$this->output( "...index $index on table $table has no field $field; added.\n" );
return false;
}
protected function doFixIpbAddressUniqueIndex() {
if ( !$this->indexHasField( 'ipblocks', 'ipb_address_unique', 'ipb_anon_only' ) ) {
$this->output( "...ipb_address_unique index up-to-date.\n" );
return;
}
$this->applyPatch(
'patch-ipblocks-fix-ipb_address_unique.sql',
false,
'Removing ipb_anon_only column from ipb_address_unique index'
);
}
* Split Mysql/Sqlite updates into their own files * Rename Update -> DatabaseUpdaters to be more consistent with DatabaseInstaller * Made DatabaseUpdaters abstract and merged the Updaters interface in, had Mysql/Oracle/Sqlite subclass it. Entry point is now factory DatabaseUpdaters::newForDB()
2010-07-20 22:28:50 +00:00
}
Reference in a new issue Copy permalink