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

1 files changed, 3 insertions, 0 deletions

diff --git a/sql/postgres/patch-l10n_cache-pk.sql b/sql/postgres/patch-l10n_cache-pk.sql
new file mode 100644
index 000000000000..b94d9d14bb26
--- /dev/null
+++ b/sql/postgres/patch-l10n_cache-pk.sql
@@ -0,0 +1,3 @@
+DROP INDEX IF EXISTS l10n_cache_lc_lang_key;
+ALTER TABLE l10n_cache
+ ADD PRIMARY KEY (lc_lang, lc_key);