RFC - Notification system about compa HOT 8 CLOSED

Thanks for this. Some comments:

1. entity_id only captures the entity's id. But we can't tell what entity that is.
2. We need to be able to know if a notification has been read by its recipient.
3. What will be the purpose of the events table?
4. We need to know when the notification was added.

from compa.

1. We could add entity_type to capture if its a post/comment etc.
2. Yeah a read field will be added to the notification subscribers.
3. Yeah I think it is redundant
4. Yeah sure a createdAtDate will be added.

from compa.

What about making it modular by separating the type of notifications ?
We have have a different table for each type of notifications like comments notifications, post notification, community notifications etc.
In this case each notification table will store its actor id and the comment/post /etc id
We will fetch from notification subscribers and join all the notification tables.

from compa.

What benefits do we get from doing it like this?

from compa.

i was confused with how we will fetch the post/comment/etc of the notification with the initial approach and hence this new suggestion.

from compa.

You need to update the issue with the new fields, etc.

from compa.

Schema design

Notification {
id
message
actor_id
entity_id
entity_type
dateCreated
}

NotificationSuscribers{
id
notification_id
user_id
read
}

from compa.

Completed with #64

from compa.