c29909e59f
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
26 lines
557 B
SQL
26 lines
557 B
SQL
-- These are carefully crafted to work in all five supported databases
|
|
|
|
CREATE TABLE /*_*/actormigration1 (
|
|
am1_id integer not null,
|
|
am1_user integer,
|
|
am1_user_text varchar(200),
|
|
am1_actor integer
|
|
);
|
|
|
|
CREATE TABLE /*_*/actormigration2 (
|
|
am2_id integer not null,
|
|
am2_user integer,
|
|
am2_user_text varchar(200)
|
|
);
|
|
|
|
CREATE TABLE /*_*/actormigration2_temp (
|
|
am2t_id integer not null,
|
|
am2t_actor integer
|
|
);
|
|
|
|
CREATE TABLE /*_*/actormigration3 (
|
|
am3_id integer not null,
|
|
am3_xxx integer,
|
|
am3_xxx_text varchar(200),
|
|
am3_xxx_actor integer
|
|
);
|