darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2026-08-17 04:58:50 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update cycle_notification_history.sql

Browse Source
This commit is contained in:
poveyd
2020-04-28 11:21:11 +01:00
committed by GitHub
parent 5b4b238098
commit 4303eba983
1 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
database_maintenance/cycle_notification_history.sql
View File

@@ -2,6 +2,7 @@
CREATE TABLE notification_history_pivot AS SELECT * FROM notification_history WHERE 1=2;
ALTER TABLE notification_history_pivot ADD PRIMARY KEY (id);
-- CREATE TRIGGER update_pivot BEFORE UPDATE ON notification_history
create trigger to update notification_history_pivot when update to notification_history
create foreign key constraints in notification_history_pivot
@@ -12,12 +13,20 @@ create remaining indices on notification_history_pivot
-- Run basic sanity checks on data in notification_history_pivot, ensuring same number of entries present in notification_history and notification_history_pivot
rename table notification_history to notification_history_old
rename table notification_history_pivot to notification_history;
ALTER TABLE notification_history RENAME TO notification_history_old;
ALTER TABLE notification_history_pivot RENAME TO notification_history;
-- Run sanity checks on data in notification_history_pivot
-- 1. Ensure same number of entries in notification_history and notification_history_pivot
-- If not then reconcile entries and add remaining entries to notification_history
-- When sure data in new notification_history table are ok:
drop table notification_history;
ALTER TABLE notification_history_old DROP CONSTRAINT notification_history_pkey; -- May not need this step.
DROP TABLE notification_history_old;
-- Must rename primary key on new notification_history table or will get issues running this script in the future.
-- This is not very nice.
ALTER TABLE notification_history DROP CONSTRAINT notification_history_pivot_pkey;
ALTER TABLE notification_history ADD PRIMARY KEY (id); -- Will create a new primary key named "notification_history_pkey".
-- Note that the only impact of these changes