From b54cec5b7a8787b3dbb0d773f93debb155dbcc9d Mon Sep 17 00:00:00 2001 From: Johannes Meyer Date: Wed, 29 Nov 2023 12:29:16 +0100 Subject: [PATCH] schema: Drop column `schedule_member.membership_hash` It's not needed by Web anymore. --- schema/pgsql/schema.sql | 1 - schema/pgsql/upgrades/019.sql | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) create mode 100644 schema/pgsql/upgrades/019.sql diff --git a/schema/pgsql/schema.sql b/schema/pgsql/schema.sql index 565921348..90d2f197b 100644 --- a/schema/pgsql/schema.sql +++ b/schema/pgsql/schema.sql @@ -111,7 +111,6 @@ CREATE TABLE schedule_member ( timeperiod_id bigint NOT NULL REFERENCES timeperiod(id), contact_id bigint REFERENCES contact(id), contactgroup_id bigint REFERENCES contactgroup(id), - membership_hash bytea DEFAULT NULL, -- There is no PRIMARY KEY in that table as either contact_id or contactgroup_id should be allowed to be NULL. -- Instead, there are two UNIQUE constraints that prevent duplicate entries. Multiple NULLs are not considered to diff --git a/schema/pgsql/upgrades/019.sql b/schema/pgsql/upgrades/019.sql new file mode 100644 index 000000000..ef17b1e0b --- /dev/null +++ b/schema/pgsql/upgrades/019.sql @@ -0,0 +1 @@ +ALTER TABLE schedule_member DROP membership_hash;