Change Details

== Summary The #checkuser extension update.php process fails for #SQLite and #postgresql as demonstrated in [[ https://integration.wikimedia.org/ci/job/quibble-vendor-sqlite-php83/6/console#console-section-12 | this failed CI run ]] and [[ https://integration.wikimedia.org/ci/job/quibble-vendor-postgres-php83/6/console#console-section-12 | this failed CI run ]] == Background - #sqlite updates often use temporary tables to make changes -- This means that when dropping or adding columns, the temporary table could not match what the current state of the table actually is -- Therefore, updates need to be skipped to ensure that #sqlite wikis do not have the updates run when the temporary table is out of date and would cause data loss / a failed query - Additionally, the `sic_updated_timestamp` column for #postgresql DBs uses the `TIMESTAMPZ` column type -- This cannot accept an empty string, but we used a default of an empty string when creating the column -- The SQL schema change for postgres DBs (and probably all other DBs) should be changed to use `null` as the default value instead of an empty string == Acceptance criteria * [ ] Running `check experimental` on #checkuser changes does not fail at the MediaWiki install stage for either #postgresql or #sqlite

== Summary The #checkuser extension update.php process fails for #SQLite and #postgresql as demonstrated in [[ https://integration.wikimedia.org/ci/job/quibble-vendor-sqlite-php83/6/console#console-section-12 | this failed CI run ]] and [[ https://integration.wikimedia.org/ci/job/quibble-vendor-postgres-php83/6/console#console-section-12 | this failed CI run ]] == Background - #sqlite updates often use temporary tables to make changes -- This means that when dropping or adding columns, the temporary table could not match what the current state of the table actually is -- Therefore, updates need to be skipped to ensure that #sqlite wikis do not have the updates run when the temporary table is out of date and would cause data loss / a failed query - Additionally, the `sic_updated_timestamp` column for #postgresql DBs uses the `TIMESTAMPZ` column type -- This cannot accept an empty string, but we used a default of an empty string when creating the column -- The SQL schema change for postgres DBs (and probably all other DBs) should be changed to use `null` as the default value instead of an empty string == Acceptance criteria * [x] Running `check experimental` on #checkuser changes does not fail at the MediaWiki install stage for either #postgresql or #sqlite

== Summary The #checkuser extension update.php process fails for #SQLite and #postgresql as demonstrated in [[ https://integration.wikimedia.org/ci/job/quibble-vendor-sqlite-php83/6/console#console-section-12 | this failed CI run ]] and [[ https://integration.wikimedia.org/ci/job/quibble-vendor-postgres-php83/6/console#console-section-12 | this failed CI run ]] == Background - #sqlite updates often use temporary tables to make changes -- This means that when dropping or adding columns, the temporary table could not match what the current state of the table actually is -- Therefore, updates need to be skipped to ensure that #sqlite wikis do not have the updates run when the temporary table is out of date and would cause data loss / a failed query - Additionally, the `sic_updated_timestamp` column for #postgresql DBs uses the `TIMESTAMPZ` column type -- This cannot accept an empty string, but we used a default of an empty string when creating the column -- The SQL schema change for postgres DBs (and probably all other DBs) should be changed to use `null` as the default value instead of an empty string == Acceptance criteria * [ * [x] Running `check experimental` on #checkuser changes does not fail at the MediaWiki install stage for either #postgresql or #sqlite