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

Update cycle_notification_history.sql

Browse Source
This commit is contained in:
poveyd
2020-05-04 16:18:06 +01:00
committed by GitHub
parent 557bf7aa7e
commit 7e4adee84b
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
database_maintenance/cycle_notification_history.sql
View File

@@ -24,7 +24,7 @@ CREATE TRIGGER update_pivot AFTER UPDATE OF notification_status, billable_units,
FOR EACH ROW FOR EACH ROW
EXECUTE PROCEDURE update_pivot_table(); EXECUTE PROCEDURE update_pivot_table();
Create foreign key constraints in notification_history_pivot with dummy names - prefix with "nh_" Create foreign key constraints in notification_history_pivot using same names as used in notification_history
insert data into notification_history_pivot in batches insert data into notification_history_pivot in batches
@@ -33,10 +33,7 @@ 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 -- Run basic sanity checks on data in notification_history_pivot, ensuring same number of entries present in notification_history and notification_history_pivot
ALTER TABLE notification_history RENAME TO notification_history_old; ALTER TABLE notification_history RENAME TO notification_history_old;
Drop constraints on notification_history_old
ALTER TABLE notification_history_pivot RENAME TO notification_history; ALTER TABLE notification_history_pivot RENAME TO notification_history;
Create foreign key constraints in notification_history using correct names. Names of constraints will now be available after step above ("Drop constraints on notification_history_old").
Drop constraints in notification_history that are prefixed with "nh_".
-- Run sanity checks on data in notification_history_pivot -- Run sanity checks on data in notification_history_pivot
-- 1. Ensure same number of entries in notification_history and notification_history_pivot -- 1. Ensure same number of entries in notification_history and notification_history_pivot