Rebecca Law f04210ba7d Refactor delete_notifications_older_than_retention_by_type to use a new strategy. ...

The insert_notification_history_delete_notifications function uses a temp table to store the data to insert and delete. This will save extra queries while performing the insert and delete operations.
The function is written in such a way that if the task is stop while processing when it's started up again it will just pick up where it left off.

I've made a decision to delete all test data in one query, I don't anticipate a problem with that.

The performance of this might also be better than last nights test because we are inserting everything we need for the NotificationHistory insert, so we don't need the join to Notifications to perform the insert.

2020-03-24 12:21:28 +00:00

28 KiB

Raw Blame History

View Raw