Automatically delete old notifications from notification_internal_activity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Medium
|
Eugene |
Bug Description
The notification_
Some of the more useless notifications could be removed periodically to make upgrades on that table a bit less painful. See http://
The worst offenders that would be safe to delete are forum post, view access, watchlist, and institution message notifications, perhaps just when they're marked as read, and are a few months old.
Most of the 'maharamessage' and ones could go too when they're old, but because that type is a bit of a dumping ground for random system notifications, we'd have to be a bit careful about it.
Others such as the admin notifications and user messages, should just hang around forever because they're not stored anywhere else.
Changed in mahara: | |
assignee: | nobody → Eugene (eugene-catalyst) |
status: | New → Fix Committed |
Changed in mahara: | |
milestone: | none → 1.4.0 |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
importance: | Undecided → Medium |
Richard - I have written a patch that should get us going on this one ;). sage', 'watchlist', 'feedback' and 'newpost' notifications.
I have added a core cronjob function that will delete stale (read and older than 21days) 'viewaccess', 'institutionmes
See the patch and let me know what you think.