repo: overhaul for multitenancy

2 files changed, 28 insertions, 0 deletions

diff --git a/migrations/2024-08-16-230507_require_guild/down.sql b/migrations/2024-08-16-230507_require_guild/down.sql
new file mode 100644
index 0000000..e7191c8
--- /dev/null
+++ b/migrations/2024-08-16-230507_require_guild/down.sql
@@ -0,0 +1,6 @@
+ALTER TABLE memes
+    ALTER COLUMN guild DROP NOT NULL;
+ALTER TABLE invocation_records
+    ALTER COLUMN guild DROP NOT NULL;
+ALTER TABLE tombstones
+    ALTER COLUMN guild DROP NOT NULL;
diff --git a/migrations/2024-08-16-230507_require_guild/up.sql b/migrations/2024-08-16-230507_require_guild/up.sql
new file mode 100644
index 0000000..06e5cd3
--- /dev/null
+++ b/migrations/2024-08-16-230507_require_guild/up.sql
@@ -0,0 +1,22 @@
+-- This migration will fail with any records in the db. If you are working with a normal server, you
+-- can run:
+--
+-- $ convert_null_guilds --guild $PREVIOUS_SINGLETENANT_GUILD
+--
+-- to set all existing db records to the specified guild. A mixed / fucked up db sceneario will
+-- require you to manually edit the db and ensure `guild` is set in `memes`, `invocation_records`,
+-- and `tombstones`.
+
+DO LANGUAGE plpgsql
+$$
+    BEGIN
+        RAISE NOTICE 'if this migration fails, consider running "convert_null_guilds"';
+    END
+$$;
+
+ALTER TABLE memes
+    ALTER COLUMN guild SET NOT NULL;
+ALTER TABLE invocation_records
+    ALTER COLUMN guild SET NOT NULL;
+ALTER TABLE tombstones
+    ALTER COLUMN guild SET NOT NULL;