Change the get notifications for a month to call a new summary table #2740
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary | Résumé
Change the get notifications for a month to call a new summary table
This is because the summary table only stores data for a month, vs day (which is what ft_notification_status does).
This table is a lot faster to answer the question how many notifications have been send by notify.
DONOT MERGE, will test this after code freeze and then merge
We can assume atleast the data in the table is correct, as if I go and query production, I see
which is the same as

which currently calling ft_notification_status
(after this PR is merged, we will be using the new table)