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

Merge branch 'cycle-notification_history-table' of github.com:alphagov/notifications-api into cycle-notification_history-table

Browse Source
This commit is contained in:
Rebecca Law
2020-05-04 17:40:21 +01:00
parent b9441c528d 7e4adee84b
commit 0d5b78149f
2 changed files with 5 additions and 6 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

6
database_maintenance/cycle_notification_history_in_batches.sql
View File

@@ -4,13 +4,15 @@ CREATE TABLE notification_history_pivot AS SELECT * from notification_history WH
CREATE TEMPORARY TABLE nh_temp AS SELECT id FROM notification_history; CREATE TEMPORARY TABLE nh_temp AS SELECT id FROM notification_history;
SELECT COUNT(*) AS 'Total number of rows in nh' FROM nh_temp; SELECT COUNT(*) AS "Total number of rows in nh" FROM nh_temp;
DELETE FROM nh_temp t DELETE FROM nh_temp t
USING notification_history_pivot p USING notification_history_pivot p
WHERE t.id = p.id; WHERE t.id = p.id;
SELECT COUNT(*) AS 'Number of rows remaining that need moving across from nh to nh_pivot' FROM nh_temp; SELECT COUNT(*) AS "Number of rows remaining that need moving across from nh to nh_pivot" FROM nh_temp;
CREATE INDEX nh_temp_idx ON nh_temp (id);
-- In each function call, using same database connection as used for the above SQL (needs to be in a transaction; this can be inside a stored function or in a transaction from the code) -- In each function call, using same database connection as used for the above SQL (needs to be in a transaction; this can be inside a stored function or in a transaction from the code)