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

Update cycle_notification_history.sql

Browse Source 
Added a few steps
This commit is contained in:
poveyd
2020-04-28 10:20:13 +01:00
committed by GitHub
parent 2d8c6ab494
commit cdbec816b3
1 changed files with 17 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
database_maintenance/cycle_notification_history.sql
View File

@@ -1,36 +1,23 @@
create table temp_notification_history (
id | uuid | not null
job_id | uuid |
job_row_number | integer |
service_id | uuid |
template_id | uuid |
template_version | integer | not null
api_key_id | uuid |
key_type | character varying | not null
notification_type | notification_type | not null
created_at | timestamp without time zone | not null
sent_at | timestamp without time zone |
sent_by | character varying |
updated_at | timestamp without time zone |
reference | character varying |
billable_units | integer | not null
client_reference | character varying |
international | boolean |
phone_prefix | character varying |
rate_multiplier | numeric |
notification_status | text |
created_by_id | uuid |
postage | character varying |
document_download_count | integer |
)
with indexes
-- Create new notification_history table and primary key.
CREATE TABLE notification_history_pivot AS SELECT * FROM notification_history WHERE 1=2;
ALTER TABLE notification_history_pivot ADD PRIMARY KEY (id);
create trigger to update temp_notification_history when update to notification_history
create foreign key constraints in notification_history_pivot
insert data into temp_notification_history in batches
create remaining indices
-- 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;
-- 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;
--- potential for data loss in this step.
rename table temp_notification_history to notification_history;