aboutsummaryrefslogtreecommitdiffstats
path: root/maintenance/sqlite/archives/patch-page_props-pp_page.sql
diff options
context:
space:
mode:
authorDaimona Eaytoy <daimona.wiki@gmail.com>2024-12-12 22:57:31 +0100
committerDaimona Eaytoy <daimona.wiki@gmail.com>2024-12-13 03:12:56 +0100
commit251f4395865f8a33bcf32c6faa11748a14753492 (patch)
tree951d03a3860e9e1851cfe8e3c1ee8ea0c4217c29 /maintenance/sqlite/archives/patch-page_props-pp_page.sql
parent589f6d5a40d7bf65250f174be1318a077733c5f5 (diff)
downloadmediawikicore-251f4395865f8a33bcf32c6faa11748a14753492.tar.gz
mediawikicore-251f4395865f8a33bcf32c6faa11748a14753492.zip
Move SQL schema and schema changes to new sql/ top-level directory
This is the standard in every extension. DB schema changes are not maintenance scripts, and therefore there's no apparent reason to have the two things together, besides historical reasons. Also, put each DB type in a separate directory, which wasn't the case for MySQL before. For SQLite and Postgres schema changes, we now follow the convention (used everywhere else, including the generateSchemaChangeSql script) of having the DB type as the last part of the path. This lets us generate schema changes for all DB types at once, and without specifying the full file path. Most files are just being renamed, the exceptions being to update references to the old location (sometimes still referencing tables.sql). Note that the old path is still referenced in the autogenerated comment of schema changes SQL files. These will be regenerated in another commit. Instead, the schema files are done now, because they're covered by DatabaseIntegrationTest that would otherwise fail. Bug: T382030 Change-Id: I3b4a614366d0bc629523ac40ce97d001f3b6bcf8
Diffstat (limited to 'maintenance/sqlite/archives/patch-page_props-pp_page.sql')
-rw-r--r--maintenance/sqlite/archives/patch-page_props-pp_page.sql17
1 files changed, 0 insertions, 17 deletions
diff --git a/maintenance/sqlite/archives/patch-page_props-pp_page.sql b/maintenance/sqlite/archives/patch-page_props-pp_page.sql
deleted file mode 100644
index b69252ac4a66..000000000000
--- a/maintenance/sqlite/archives/patch-page_props-pp_page.sql
+++ /dev/null
@@ -1,17 +0,0 @@
--- This file is automatically generated using maintenance/generateSchemaChangeSql.php.
--- Source: maintenance/abstractSchemaChanges/patch-page_props-pp_page.json
--- Do not modify this file directly.
--- See https://www.mediawiki.org/wiki/Manual:Schema_changes
-DROP INDEX pp_propname_page;
-DROP INDEX pp_propname_sortkey_page;
-CREATE TEMPORARY TABLE /*_*/__temp__page_props AS
-SELECT pp_page, pp_propname, pp_value, pp_sortkey
-FROM /*_*/page_props;
-DROP TABLE /*_*/page_props;
-CREATE TABLE /*_*/page_props ( pp_page INTEGER UNSIGNED NOT NULL, pp_propname BLOB NOT NULL, pp_value BLOB NOT NULL, pp_sortkey DOUBLE PRECISION DEFAULT NULL, PRIMARY KEY(pp_page, pp_propname) );
-INSERT INTO /*_*/page_props ( pp_page, pp_propname, pp_value, pp_sortkey )
-SELECT pp_page, pp_propname, pp_value, pp_sortkey
-FROM /*_*/__temp__page_props;
-DROP TABLE /*_*/__temp__page_props;
-CREATE UNIQUE INDEX pp_propname_page ON /*_*/page_props (pp_propname, pp_page);
-CREATE UNIQUE INDEX pp_propname_sortkey_page ON /*_*/page_props (pp_propname, pp_sortkey, pp_page); \ No newline at end of file