From 251f4395865f8a33bcf32c6faa11748a14753492 Mon Sep 17 00:00:00 2001 From: Daimona Eaytoy Date: Thu, 12 Dec 2024 22:57:31 +0100 Subject: 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 --- sql/mysql/patch-image-img_timestamp.sql | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 sql/mysql/patch-image-img_timestamp.sql (limited to 'sql/mysql/patch-image-img_timestamp.sql') diff --git a/sql/mysql/patch-image-img_timestamp.sql b/sql/mysql/patch-image-img_timestamp.sql new file mode 100644 index 000000000000..8442f50237e9 --- /dev/null +++ b/sql/mysql/patch-image-img_timestamp.sql @@ -0,0 +1,2 @@ +ALTER TABLE /*_*/image + MODIFY img_timestamp BINARY(14) NOT NULL; -- cgit v1.2.3