Incubator » CB Activity

Split notifications into a new database table as it's causing activity table optimization problems. A new API should be made as well that'd just extend the Activity class. This likely means we can get rid of the read table and just make the read state a column for the notification (only the recipient can make it read).

Notification table should also extend the Activity table. For all intended purposes the Notifications should just be treated like Activity in nearly every way. So no new triggers specifically for notifications. The extensions to the Activity table are simply a "user" and "read" column. User determines the notification recipient and read determines if the recipient has read the notification. All the conditions against asset looking for notifications can simply be changed over to do an instanceof check for Notifications stream or NotificationTable as needed.

This should also work with the global asset to allow for global notifications.

Removing the read table may not work for cases like global notifications since the read state would need to be per person. Conversations would basically need to be the same as well. So keep, but optimize further, the read table for keeping track of what notifications have been read.